At 14:51 3/26/2004, Kirk Friggstad wrote: >You realize that XMail can listen on more than one port for SMTP, right? >Check out the -SI commandline parameter in the documentation. For example: > -SI 192.168.0.1:25 -SI 192.168.0.1:2500 >would set XMail to listen to port 25 and 2500 for incoming SMTP connections >on 192.168.0.1 - no tunneling software, etc. needed. For the Windows >version, you'll need to add this to the XMAIL_CMD_LINE value of the >HKEY_LOCAL_MACHINE\SOFTWARE\GNU\XMail\ registry key. > >We've been using this type of configuration for quite some time to help our >remote users who are stuck with Earthlink or other ISPs that block port 25 >outgoing. > >There you go - no muss, no fuss, no Cygwin, no SSL/SSH tunneling... hope >that helps!
OK, I added the second -SI option on the MAILCMD_LINE registry entry, but I'm having a bit of problem. I currently have: -Pl -Sl 66.219.172.36:25 -SI 66.219.172.36:587 -Ql -Cl -Ll Problem is, with it set this way, it answers on port 587, but *not* on port 25... Is there some other configuration that has to be done in connection with this? If I remove the second -SI entry, it works correctly. (Also, it doesn't matter which order I list them in, as long as the :587 entry is in there, that's the only port it answers on...) - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
