Blocking and a shuffle, then. For a while (previous admin), emails sent
from the mail server were listed by the FQDN instead of just the domain,
emails showing up as originating from <user>@<machine>.<domain>.<tld>.
So we still have valid emails being sent to the FQDN of the machine.
It'd be a matter of finding out which, nailing those down, -then- we can
switch things around.
I guess I'm just too used to having the server itself handling scanning
and everything, blocking SMTP access to it just didn't come to mind as
an option... :7
Amavisd-new will still be used on the machine, watching our out-going
mail. The Barracuda box is directional, and has configurations to be
either "incoming" or "outgoing." So Amavis will hang around, watching
outgoing mail to make sure we don't become a problem in case of virus
infection.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
