Can you tell me what happens when the receiving mailserver is offline?
If messages are kept in outgoing queue, for how long?
Could ESVA then also serve as a security for downed mailservers?
Also could it be used to store customers mails for potential restore option?
Can you tell me what happens when the receiving
mailserver is offline?
Postfix will keep retrying. Deferred messages can be found in the deferred directory.
If messages are kept in outgoing queue, for how
They are moved to deferred - Not sure how long for though. I'll have to check.
Could ESVA then also serve as a security for downed
Yes - It does this very well, but for how long depends on how long it will keep messages for in the deferred queue.
Also could it be used to store customers mails for
potential restore option?
Absolutely - You will need to turn archiving on in MailScanner.conf (maybe via the webmin applet...). I'm not sure if this can be configured per domain etc. as I haven't tried this feature out.
Be aware that this will eat disk - It might be prudent to create a new vmdk and attach it to your ESVA if you want this functionality - that way you can keep this same archive through ESVA versions.
postfix can check a file for valid recipients - you just need to configure this functionality.
Can you dump a list of valid recipients to a text file?
That is perfect!
That make ESVA a 3-in-one product
E-mail security, Backup MX functionality, and e-mail storage
Looking forward to your reply on how long it holds the deferred mails...
I will try the mail archiving function. Off course it will need more storage, but that is up to the potential customers to pay.
Keep up the good work!
If anybody is interested, I migrated my postgrey berkeley db from ESVA 1.5 to 1.6 by simply copying the contents of the /var/spool/postfix/postgrey from the old version to the new one. I had to reset the permissions on that folder, also.
This was important as I didn't want postgrey to have to re-learn everything.
One other thing I did was change the delay to 1 in the options for postgrey. I added --delay=1 to the OPTIONS line in /etc/init.d/postgrey. It seems that spam never really retries so a delay longer just annoys my users. I'll update here if this lets through a lot of spam or not.
Andy, Awesome product![/b] This tool you created is perfect for those of us who run their own personal small time mail servers. Please tell us you will keep up the good work and keep it free for us little people!
The only problem I'm having seems to be the DCC checking, it almost always says "3.00 DCC_CHECK Listed in DCC (http://rhyolite.com/anti-spam/dcc/)" even for special one time custom generated emails which can't be listed in the DCC. Any idea why this would be happening and the best way to resolve the issue?
Also, is there any way to see statistics for greylisting? I was running v188.8.131.52 where greylisting was not running and seen a lot of Spam being caught, but with v184.108.40.206 MailWatch sees almost no Spam which means greylisting is working VERY well. Just wondering how well.
Can you be a little more specific on where in /etc/init.d/postgrey to insert the delay line?
Also is the number 1 in seconds?
I also think it would be nice to be able to see what is delayed...
I have allready encountered a friend whose emails to me returned as rejected from his mailserver.
Also it would be nice to overview the delayed messages, so one could manually whitelist those that are definately not spammers.
Here is the section in /etc/init.d/postgrey:
\# Source an auxiliary options file if we have one, and pick up OPTIONS,
As for how long the delay is... i'm no postgrey expert or nuthin' so I don't know if it's minutes of seconds, but i'm pretty sure its seconds. It has allowed more spam through than previously, though, but so far I'm still happy about the trade off.
as far as viewing the postgrey delays...
I have a little php script that parses the maillog and shows whats been delayed and what has been sent for each user. I'll put the code up here when I get to work tomorrow. It's really very primitive now, but its still useful.
I think there will always be a need for a free product - just like HedHat have Fedora, I think I'll always have a free version of ESVA...
Anyway. Not sure about the DCC check - sounds like a strange one to me... Maybe someone else has seen something like that?
For stats, the best way is to point your browser at esva (http - not https for webmin) and click on the mailgraph link. The rejected messages are from postgrey and postfix checks (mostly postgrey though)
Nice one - I'd like to see that one - With your permission I could host it on the site for others to download and install.
-Obviously credit would be given for this and any other contributions!
Unfortunately there are some poorly implemented (RFC wise) MTAs out there that:
a) Don't interpret the 450 message correctly
b) Don't retry at all or have such a long retry that it's as good as useless.
If anyone comes across any domains that don't cope with Greylisting, please let me know so that I can update the default postgrey whitelist and make it available.
Clever regex is always appreciated in these whitelist rules rather than screens full of IP addresses...
I think that this forum is too limited for the wide ranging discussions that are held in here, so I'm thinking about adding a forum to global-domination.org.
Does anyone have any suggestions?
(it's a shared (linux based) service, but can utilise PHP/CGI and MySql...)
phpbb is what I'd recommend for free board... but I've had some problems with it not coping very well for high traffic sites... shouldn't be a problem for what's been discussed here so far.