Language:
switch to room list switch to menu My folders
Go to page: First ... 19 20 21 22 [23] 24 25 26 27 ... Last
[#] Mon Jan 29 2018 20:11:37 EST from travisr @ Uncensored

Subject: Re: Smart Host Auth

[Reply] [ReplyQuoted] [Headers] [Print]

 

Mon Jan 29 2018 13:39:31 EST from IGnatius T Foobar @ Uncensored Subject: Re: Smart Host Auth
i saw that traffic in my firewall just fine. Connection closed with a
tcp-fin to the correct destination IP. So i know my other settings
are fine. now when I change just the username to the mail address,
the server stops even trying to connect to the smart host

The short answer is that the string you put in for your smart-host gets fed into libcurl as the CURLOPT_URL. Citadel Server since version 910 has started using libcurl to do all of the outbound protocol handling, so whatever libcurl accepts, we accept.

What you can do to troubleshoot, is run citserver with the highest level of logging (using the -x9 option) and filter the log for lines beginning with "smtpclient:" to see what it's doing. I'm pretty sure it *does* accept a username with "@" in it.

OK, thank you for the reply. I understand basically what you are saying, but I might need a little nudge on doing it right.

I did some googling and I checked the Citadel Documentation but I'm a tad stuck.

I did "ls /etc/init.d" and saw the citadel file. I then did "cat /etc/init.d/citadel" and saw that this seemed to be the file i need to edit. Im just not sure where to put the -x9 command switch I think here at the end?:
CITADEL_DIR=/usr/local/citadel -x9

Or would it be here?:

case "$1" in

start)          echo -n "Starting Citadel... "
                if $CITADEL_DIR/citserver -d -h$CITADEL_DIR -x9

I'm not the best a Linux obviously, but I've done OK so far with what I do know and google. If it helps, this is on a raspberry Pi where I also installed Pi-Hole. I only need this for 3 mail boxes (might grow to 5 or so) and I'm trying to ditch an old server with exchange.

After add the -x9 i just restart the Pi right? then where does it save the logs?

Again, I appreciate anything you can help me with. I'm pretty sure this is the last part I need to make this all function.



[#] Mon Jan 29 2018 21:22:55 EST from IGnatius T Foobar @ Uncensored

Subject: Re: Smart Host Auth

[Reply] [ReplyQuoted] [Headers] [Print]

I did "ls /etc/init.d" and saw the citadel file. I then did "cat
/etc/init.d/citadel" and saw that this seemed to be the file i need
to edit. Im just not sure where to put the -x9 command switch I think
here at the end?:

Try this, if you can tolerate a few minutes of downtime:

First stop the running server by doing:

/etc/init.d/citadel stop

Once your server shuts down, you can run it in the foreground:

cd /usr/local/citadel
./citserver -x9

That way, you can watch everything it's doing. If you want to filter the output:

./citserver -x9 2>&1 | grep smtpclient:

You can stop the server by pressing Ctrl-C and waiting for it to clean up and stop, then run it in the background again with:

/etc/init.d/citadel start

[#] Mon Jan 29 2018 22:19:27 EST from travisr @ Uncensored

Subject: Re: Smart Host Auth

[Reply] [ReplyQuoted] [Headers] [Print]

 

Mon Jan 29 2018 21:22:55 EST from IGnatius T Foobar @ Uncensored Subject: Re: Smart Host Auth

Try this, if you can tolerate a few minutes of downtime:

First stop the running server by doing:

/etc/init.d/citadel stop

Once your server shuts down, you can run it in the foreground:

cd /usr/local/citadel
./citserver -x9

That way, you can watch everything it's doing. If you want to filter the output:

./citserver -x9 2>&1 | grep smtpclient:

You can stop the server by pressing Ctrl-C and waiting for it to clean up and stop, then run it in the background again with:

/etc/init.d/citadel start

That really helped narrow down my problem! Here is what I get when I tried to send an email with the full Smart Host Auth User name (smtp://ME@DOMAIN.com:abc123@asp-submit.reflexion.net:2525)
citserver[12220]: smtpclient: 381 attempting delivery now
citserver[12220]: smtpclient: smtp_attempt_delivery(380, travisrxxxx@gmail.com)
citserver[12220]: smtpclient: trying smtp://travis@DOMAIN.com:abc123@asp-submit.reflexion.net:2525/DOMAIN.com
citserver[12220]: smtpclient: libcurl returned 6 (Couldn't resolve host name) , SMTP response 0
citserver[12220]: smtpclient: recp: <travisrxxxx@gmail.com> , result: 421 (Domain service not available, closing transmission channel)
citserver[12220]: smtpclient: submission age: 0d0h0m27s

So it does look like its passing it correctly for the most part, but the "Couldn't resolve host name" caught my eye. So I logged into Pi-Hole and found that it was trying to resolve this:
DOMAIN.com:abc123@asp-submit.reflexion.net.DOMAIN.com
(and it also tried to resolve:)
DOMAIN.com:abc123@asp-submit.reflexion.net

Obviously that didn't resolve right, hence why I didn't see any connection attempts in the firewall the other day. (I did confirm that Pi-Hole is not blocking the DNS request)

Just to see what I would get, I change the username to just "travis" (smtp://travis:abc123@asp-submit.reflexion.net:2525)
In Pi-hole I see the correct DNS request! (asp-submit.reflexion.net) and this is what Citadel came back with:
citserver[12220]: smtpclient: 386 attempting delivery now
citserver[12220]: smtpclient: smtp_attempt_delivery(385, travisrxxxx@gmail.com)
citserver[12220]: smtpclient: trying smtp://travis:abc123@asp-submit.reflexion.net:2525/DOMAIN.com
citserver[12220]: smtpclient: libcurl returned 67 (Login denied) , SMTP response 250
citserver[12220]: smtpclient: recp: <travisrxxxx@gmail.com> , result: 250 (Requested mail action completed and OK)
citserver[12220]: smtpclient: submission age: 0d0h0m17s

The DNS request was correct, it contacted the smart host and the smart host denied me (as expected with bad login info) and I see a firewall log entry.

So the question is, does the problem stem from how Citadel is making the DNS request, or how Pi-hole is interpreting the request. With what I know of networking and DNS, it seems to me that the issue would be how Citadel is making its DNS request
Would you agree? What would my next step be to fix this? (and the other big question, how do I get you some beer donation money? lol)

 



[#] Tue Jan 30 2018 04:25:04 EST from mkuhn @ Uncensored

Subject: Citadel 8.24 & Spamassassin

[Reply] [ReplyQuoted] [Headers] [Print]

Hi team,

I am running Citadel for a while and decided to install spamassassin this week.  Install went fine.  Spamd identified test spam mail OK but citserver did not reject that incoming email.  Here is the log:

Jan 30 08:18:29 mail citserver[425]: Connecting to SpamAssassin at <127.0.0.1>

Jan 30 08:18:29 mail spamd[1630]: spamd: connection from localhost [127.0.0.1]:40856 to port 783, fd 5

Jan 30 08:18:29 mail spamd[1630]: spamd: still running as root: user not specified with -u, not found, or set to root, falling back to nobody

Jan 30 08:18:29 mail spamd[1630]: spamd: checking message <000b01d3999a$87039a90$950acfb0$@web.de> for (unknown):65534

Jan 30 08:18:33 mail citserver[425]: CC[134]MSGFinal selection: Sent Items ()

Jan 30 08:18:33 mail citserver[425]: CC[134]MSG<> 0 new of 0 total messages

Jan 30 08:18:33 mail spamd[1630]: spamd: identified spam (999.5/2.0) for (unknown):65534 in 3.1 seconds, 5697 bytes.

Jan 30 08:18:33 mail spamd[1630]: spamd: result: Y 999 - FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,GTUBE,HTML_MESSAGE,MSGID_FROM_MTA_HEADER,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_PASS,T_RP_MATCHES_RCVD scantime=3.1,size=5697,user=(unknown),uid=65534,required_score=2.0,rhost=localhost,raddr=127.0.0.1,rport=40856,mid=<000b01d3999a$87039a90$950acfb0$@web.de>,autolearn=no autolearn_force=no

 

Jan 30 08:18:33 mail citserver[425]: 156434: from=<xyz@web.de>, nrcpts=1, relay=mout.web.de [212.227.15.14], stat=250 Message accepted.

Is this a bug or a misconfiguration on my end?





[#] Wed Jan 31 2018 07:11:51 EST from mkuhn @ Uncensored

Subject: Re: Citadel 8.24 & Spamassassin

[Reply] [ReplyQuoted] [Headers] [Print]

Figured it out.  Misconfig in the Webcit Admin panel's SMTP tab.  I had a checkmark to mark spam instead of rejecting. Oh, well.



[#] Thu Feb 01 2018 00:10:29 EST from EbolAmoeba @ Uncensored

Subject: Big fan... Big, frustrated, adoring fan

[Reply] [ReplyQuoted] [Headers] [Print]

I have just recently tried installing, and running, citadel. I love it! The idea, the execution, the fight! I've been playing for a few days, and getting errors like c_port_number and c_ctdluid bugs. When I attempt repair using recommended fixes, more errors appear. If 32-bit Ubuntu 16.04 is my root issue, I'm happy to change vector/host. I'm trying to avoid compiling from [my own poorly modified] source code. 

 

If no one else is running into this, I'm going to break into an Arch install next to see if it works better. 

TIA for any help!



[#] Thu Feb 01 2018 00:14:06 EST from EbolAmoeba @ Uncensored

Subject: Re: Big fan... Big, frustrated, adoring fan

[Reply] [ReplyQuoted] [Headers] [Print]

Also of note, the base build breaks immediately if I modify any settings under Administrator. Including just going in, changing nothing, and clicking save.



[#] Thu Feb 01 2018 18:03:44 EST from travisr @ Uncensored

Subject: Re: Smart Host Auth

[Reply] [ReplyQuoted] [Headers] [Print]

 

So the question is, does the problem stem from how Citadel is making the DNS request, or how Pi-hole is interpreting the request. With what I know of networking and DNS, it seems to me that the issue would be how Citadel is making its DNS request
Would you agree? What would my next step be to fix this?

Does anyone have a suggestion on how to work around this issue? The username I have to use for my smarthost is an email address, and the "@" symbol in the username causes Citadel to send the wrong DNS request starting from the first @ symbol. I made a static DNS entry on Pi-Hole just to test it as if it got the right IP, and I get a "login denied" from the smart host. I don't think its passing the login info properly even after it connects to the smart host all because of the @ symbol in the username. I know the username and password is correct because it works on my current server.

Any help would be appreciated because I'm pretty sure this is the last piece I need to get everything working and finally get rid of my old crappy, power hogging server.

Thanks!



[#] Fri Feb 02 2018 15:28:38 EST from Haven @ Uncensored

Subject: Re: Smart Host Auth

[Reply] [ReplyQuoted] [Headers] [Print]

 

Thu Feb 01 2018 18:03:44 EST from travisr @ Uncensored Subject: Re: Smart Host Auth

 

So the question is, does the problem stem from how Citadel is making the DNS request, or how Pi-hole is interpreting the request. With what I know of networking and DNS, it seems to me that the issue would be how Citadel is making its DNS request
Would you agree? What would my next step be to fix this?

Does anyone have a suggestion on how to work around this issue? The username I have to use for my smarthost is an email address, and the "@" symbol in the username causes Citadel to send the wrong DNS request starting from the first @ symbol. I made a static DNS entry on Pi-Hole just to test it as if it got the right IP, and I get a "login denied" from the smart host. I don't think its passing the login info properly even after it connects to the smart host all because of the @ symbol in the username. I know the username and password is correct because it works on my current server.

Any help would be appreciated because I'm pretty sure this is the last piece I need to get everything working and finally get rid of my old crappy, power hogging server.

Thanks!



DNS is the translation of a hostname to an IP address.  So if your smarthost is located at mail.server.tla, DNS will then translate that to 10.2.55.186.   When you connect to the smarthost via a URL it should look like smtp://mail.server.tla/?user@server.tla/mailbox/.  (this is more or less a guess at the URL, it probably looks way different)  So DNS would only effect the mail.server.tla.    

 

Domain names do not allow for symbols in them other than "-".   DNS would have no idea what to do with anything else.  



[#] Fri Feb 02 2018 15:37:14 EST from Haven @ Uncensored

Subject: Re: Smart Host Auth

[Reply] [ReplyQuoted] [Headers] [Print]

Sorry, I didn't read the whole thread.  I don't usually provided support for Citadel.   I haven't run a Citadel since 2011, so I am a bit out of what was there for options.  So I could be very wrong on what is happening.  



[#] Fri Feb 02 2018 16:01:12 EST from travisr @ Uncensored

Subject: Re: Smart Host Auth

[Reply] [ReplyQuoted] [Headers] [Print]

This section in Citadel's documentation called Configuring Relaying show that the URL syntax should look like this

[smtp[s]://][username:password@]host[:port]

But the problem is Citadel takes what is listed after the @ symbol and makes a DNS query based off of that. This works until the user name also has an @ symbol in it. So when I configure this:
smtp://ME@DOMAIN.com:abc123@asp-submit.reflexion.net:2525
it tries to make a DNS request for "DOMAIN.com:abc123@asp-submit.reflexion.net".

Its using the first @ symbol it comes across to form its DNS request, which in my case is the wrong one, and even when I make an entry in my DNS server to give it a valid IP for that, the smart-host doesn't accept the login. I don't think that Citadel is passing the credentials properly either because its getting tripped up on the extra @ symbol in the URI - I just need a workaround or maybe even a patch to have Citadel separate the pieces of the URI right. Maybe instead of having the user/admin type it in as a whole string, make a couple fields to collect the info and then assemble each function off of those fields.

I'm not good at the programming side of things, but I am pretty eager for some way to make this work.



[#] Sat Feb 03 2018 19:25:07 EST from IGnatius T Foobar @ Uncensored

Subject: Re: Smart Host Auth

[Reply] [ReplyQuoted] [Headers] [Print]

This section in Citadel's documentation called Configuring Relaying show that the URL syntax should look like this

[smtp[s]://][username:password@]host[:port]

But the problem is Citadel takes what is listed after the @ symbol and makes a DNS query based off of that. This works until the user name also has an @ symbol in it. So when I configure this:
smtp://ME@DOMAIN.com:abc123@asp-submit.reflexion.net:2525
it tries to make a DNS request for "DOMAIN.com:abc123@asp-submit.reflexion.net".

Yes, my testing does reproduce that same effect.

When you specify a Smart Host for outbound delivery of all mail, Citadel passes that string along to libcurl as the CURLOPT_URL for SMTP delivery.  (Citadel uses libcurl for all protocol handling.)  So unfortunately it's not something we are able to change in Citadel to make it properly handle a username with an @ character in it.  (Seems very silly, doesn't it?  I can't believe we're the first ones to have this problem.)

You indicated that you're not a programmer but you are willing to help in developing a solution.  Would it be possible for you to post this problem on the libcurl mailing list or support channels, and see what their experts have to say about it?  In that context, Citadel is not really relevant except that it is "an application using libcurl for SMTP delivery" and the smtp://ME@DOMAIN.com:abc123@asp-submit.reflexion.net:2525 is the CURLOPT_URL being used by the program.



[#] Sat Feb 03 2018 19:28:25 EST from IGnatius T Foobar @ Uncensored

Subject: Re: Big fan... Big, frustrated, adoring fan

[Reply] [ReplyQuoted] [Headers] [Print]

I have just recently tried installing, and running, citadel. I love it! The idea, the execution, the fight! I've been playing for a few days, and getting errors like c_port_number and c_ctdluid bugs. When I attempt repair using recommended fixes, more errors appear. If 32-bit Ubuntu 16.04 is my root issue, I'm happy to change vector/host. I'm trying to avoid compiling from [my own poorly modified] source code. 

Thanks for the kind words! For some reason, we do keep having a nagging problem with the port number setting, but the good news is that you should be able to just set those values in your system configuration and they will stay set.

Ubuntu repos are a bit behind the cutting edge, because first the packager for Debian has to do an update, then it goes through the whole Debian testing process, and then it flows from Debian over to Ubuntu. Sometimes that can take time (even months). For a new installation you might want to try out the Easy Install method instead.



[#] Sat Feb 03 2018 19:40:44 EST from wylekyote @ Uncensored

Subject: Server down with libev: ev_io_start called with corrupted watcher

[Reply] [ReplyQuoted] [Headers] [Print]

Starting it up it goes through the mail queue then aborts with a core dump

 

citserver[3945]: No external notifiers configured on system/user

citserver[3945]: -- db checkpoint --

citserver: ev.c:3846: ev_io_start: Assertion `("libev: ev_io_start called with corrupted watcher", ((WL)w)->next != (WL)w)' failed.

Aborted (core dumped)

 

 

 

Version info as follows -- off the debian repos 

 

 

citserver[3945]:  

citserver[3945]:  

citserver[3945]: *** Citadel server engine v8.24 (build 5644ab7) ***

citserver[3945]: Copyright (C) 1987-2014 by the Citadel development team.

citserver[3945]: This program is distributed under the terms of the GNU General Public License.

citserver[3945]:  

citserver[3945]: Called as: citserver

citserver[3945]: libcitadel(unnumbered)

citserver[3945]: Loading citadel.config

citserver[3945]: Acquiring control record

citserver[3945]: master_startup() started

citserver[3945]: Opening databases

citserver[3945]: bdb(): open_databases() starting

citserver[3945]: Compiled db: Berkeley DB 4.7.25: (March 22, 2017)

citserver[3945]:   Linked db: Berkeley DB 4.7.25: (March 22, 2017)

citserver[3945]: Calculated dbversion: 4007025

citserver[3945]:   Previous dbversion: 4007025

citserver[3945]: Linked zlib: 1.2.3

citserver[3945]: bdb(): Setting up DB environment

citserver[3945]: dbenv->open(dbenv, /var/lib/citadel/data/, 5461, 0)

citserver[3945]: DB: Finding last valid log LSN: file: 302198 offset 2277753

citserver[3945]: DB: Recovery starting from [302198][2273555]

citserver[3945]: DB: Recovery complete at Sun Feb  4 00:36:53 2018

citserver[3945]: DB: Maximum transaction ID 80000023 Recovery checkpoint [302198][2278832]

citserver[3945]: Starting up DB

 
 
please help 


[#] Sun Feb 04 2018 02:57:05 EST from bitpilot @ Uncensored

Subject: I'm enjoying this BBS Groupware app quite a bit

[Reply] [ReplyQuoted] [Headers] [Print]

Went missing the rain-forest or all the BBS years. I'm really enjoying your app you folks built, need a rusty coder? Installed this thing with the easy installers and she goes real good. No show-stoppers I can see right.

I'm going to use it for several years during my kids secondary education so would like to contribute to it in some ways.

If there's any pointers on clam-daemon and other resource sucking behemoths for AV I'd be mighty grateful. I'm running off a first gen raspberry pi and whilst that rockets with your app - the Clam AV stuff tends to rip it a new one, especially in terms of nuking all the memory. I dunno, maybe auto security updates is enough right?

 

 



[#] Sun Feb 04 2018 03:05:14 EST from bitpilot @ Uncensored

Subject: Re: I'm enjoying this BBS Groupware app quite a bit

[Reply] [ReplyQuoted] [Headers] [Print]

Might aswell go for the double jeopardy while I'm here :) Are their any scripts floating around for backing it up incase I nuke it? Highly likely given my affinity with random button pressing to see what gives.



[#] Sun Feb 04 2018 03:41:12 EST from bitpilot @ Uncensored

Subject: Giving webcit awesome process durability

[Reply] [ReplyQuoted] [Headers] [Print]

Hi folks, here's a little trick I use to keep Webcit process running even when it falls over with segmentation fault. That way Webcit and Citadel just keep on working - pretty handy if you have a bunch of folks using it.

cd ~

mkdir script

cd script

nano survive-webcit.sh

chmod +x survive-webcit.sh

 

... copy/paste this code here ...

#!/bin/sh

service=webcit

case  "$(pidof $service | wc -w)" in

0) echo "$service is not running!!!"

nohup '/usr/local/webcit/webcit' &

;;

1) echo "$service is  running!!!"

;;

*) echo "multiple instances running"

;;

esac

... snip here ...
 
 
Then..
Ctrl-O to save, Save As survive-webcit.sh
Ctrl-X to get the hell out of there back to terminal
Now your back in terminal right so fire up crontab as whatever that user is running webcit.
Probably just your normal user unless you did the Easy Install as SU or a Sudoer.
 
type the command terminal... crontab -e
 
add this cronjob... */1  *  *   *   *    /usr/bin/nohup /bin/sh /home/pi/script/survive-webcit.sh &
 
That's all..
 
Now some folks may not have nohup installed so if you need it, sudo yum install nohup or sudo apt-get install nohup
That's for Rehat or Debian/Ubuntu based distro's respectively.
 
Too easy huh?
 
 


[#] Sun Feb 04 2018 16:22:10 EST from bgerum @ Uncensored

Subject: Re: citadel refuses to start after OpenSuSE upgrade - cursor still in prog

[Reply] [ReplyQuoted] [Headers] [Print]

 

Mon Jan 29 2018 18:34:53 EST from bgerum @ Uncensored Subject: Re: citadel refuses to start after OpenSuSE upgrade - cursor still in prog

 

Mon Jan 29 2018 13:35:33 EST from IGnatius T Foobar @ Uncensored Subject: Re: citadel refuses to start after OpenSuSE upgrade - cursor still in prog
thanks for the reply. Unfortunately it seems the last version supplied by
the
homueller SuSE repo which is linked in the citadel.org doku ist 824.


Is there another rpm source?

I'm not aware of another RPM source. You could switch to Easy Install, which works on all distributions, but you'll have to move your data files to another directory first.

I used the Easy Install a long time ago, but the RPM version ist much more integrated in the OpenSuSE environment, not only directory-wise but also regarding startscripts, updating etc.

Do you think you could give Mr. homueller a hint there are new citadel versions out there? 



Ok, I found another OpenSuSE rpm source:

https://download.opensuse.org/repositories/home:/stefjakobs:/citadel-testing

it does provide citadel-9.01-13.19.x86_64, I installed it although it is compiled for the tumbleweed version of OpenSuSE, not leap which is what i use.

however, my database upgrade problem still remains:

citserver[14575]: Checking directory access
citserver[14575]: Opening databases
citserver[14575]: bdb(): open_databases() starting
citserver[14575]: Compiled db: Berkeley DB 4.8.30: (March 31, 2016)
citserver[14575]:   Linked db: Berkeley DB 4.8.30: (October 21, 2013)
citserver[14575]: Calculated dbversion: 4008030
citserver[14575]:   Previous dbversion: 4008030
citserver[14575]: Linked zlib: 1.2.8
citserver[14575]: bdb(): Setting up DB environment
citserver[14575]: dbenv->open(dbenv, /var/lib/citadel/data/, 10899, 0)
citserver[14575]: DB: Finding last valid log LSN: file: 6494 offset 9355549
citserver[14575]: DB: Recovery starting from [6494][9355421]
citserver[14575]: DB: Recovery complete at Sun Feb  4 22:10:24 2018
citserver[14575]: DB: Maximum transaction ID 80000024 Recovery checkpoint [6494][9355549]
citserver[14575]: Starting up DB
citserver[14575]: Checking floor reference counts
citserver[14575]: bdb(): cursor still in progress on cdb 04: can't begin transaction during r/o cursor
citserver[14575]: citserver is stopping in order to prevent data loss. uid=0 gid=0 euid=0 egid=0


 



[#] Sun Feb 04 2018 16:42:59 EST from travisr @ Uncensored

Subject: Re: Smart Host Auth

[Reply] [ReplyQuoted] [Headers] [Print]

 

Yes, my testing does reproduce that same effect.

When you specify a Smart Host for outbound delivery of all mail, Citadel passes that string along to libcurl as the CURLOPT_URL for SMTP delivery.  (Citadel uses libcurl for all protocol handling.)  So unfortunately it's not something we are able to change in Citadel to make it properly handle a username with an @ character in it.  (Seems very silly, doesn't it?  I can't believe we're the first ones to have this problem.)

You indicated that you're not a programmer but you are willing to help in developing a solution.  Would it be possible for you to post this problem on the libcurl mailing list or support channels, and see what their experts have to say about it?  In that context, Citadel is not really relevant except that it is "an application using libcurl for SMTP delivery" and the smtp://ME@DOMAIN.com:abc123@asp-submit.reflexion.net:2525 is the CURLOPT_URL being used by the program.

I have a post over at libcurl under the users section. If I get a resolution or something to get me in the right direction, I'll try and post back here with an update.



[#] Wed Feb 07 2018 05:54:31 EST from ematos @ Uncensored

Subject: Forward an email to a PHP script

[Reply] [ReplyQuoted] [Headers] [Print]

Hello,

I'm a Citadel novice. I want to forward an email sent to an room to be processed by a PHP script. The PHP script will need to have access to the data from message (or at least, the message source text, when I can use a library to extract the info). I have read the FAQ

"How do I automatically forward all mail to a remote email address somewhere?"

but it is not exactly what I need. Is it possible to do what I need in Citadel?

Thanks for attention,

Ely

 



Go to page: First ... 19 20 21 22 [23] 24 25 26 27 ... Last