uro jotne wrote:
I had to put the 196.168.2 (the LAN) in /etc/tcp.smtp. However, I still have 172.16.0 (DMZ, where the mail server is) in /home/vpopmail/etc/tcp.smtp. Now it works, but I would sleep better if I understood how vpopmail uses the two files /etc/tcp.smtp and /home/vpopmail/etc/tcp.smt
tcpserver uses one CDB file- that being a compiled database in CDB format with the keys (domains) and their values.Whichever file is in your -x parameter for tcpserver is the one that is used. The other is not used at all by your SMTP server.Given that, vpopmail has a neat feature of POP-before-SM
I had to put the 196.168.2 (the LAN) in /etc/tcp.smtp. However, I still have 172.16.0 (DMZ, where the mail server is) in /home/vpopmail/etc/tcp.smtp. Now it works, but I would sleep better if I understood how vpopmail uses the two files /etc/tcp.smtp and /home/vpopmail/etc/tcp.smtp. I mistakenly th
MT wrote:
The mail server resides at a 172.16.0 net and the client machines at a
192.168.2.0 net. If I have understood the documentation correctly,
vpopmail must be configured with "--enable-roaming-users" if the
client machines are on a different net. Correct?
No.
If you have clients at stat
The mail server resides at a 172.16.0 net and the client machines
at a 192.168.2.0 net. If I have understood the documentation
correctly, vpopmail must be configured with "--enable-roaming-
users" if the client machines are on a different net. Correct?
The entry in /home/vpopmail/etc/tcp.sm
uro jotne wrote:
I have run into some strange trouble with a fresh installation of netqmail-1.05 /
vpopmail-5.2.2 (on Debian Sarge). I have run inst_check, which reassuringly reported
"Congratulation, your installation looks good!". I configured vpopmail thus:
./configure --enable-roaming-user
