Re: [courier-users] courier-mta and amavis-new +clamAV

This is a discussion on Re: [courier-users] courier-mta and amavis-new +clamAV within the Courier-Imap forums, part of the Mail Servers and Related category; Hello :), Thanks for all the response. I already use Spamd with courier-mta and very happy with the combo. I ...


Go Back   Usenet Forums > Mail Servers and Related > Courier-Imap

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 10-31-2007
FM
 
Posts: n/a
Default Re: [courier-users] courier-mta and amavis-new +clamAV

Hello :),
Thanks for all the response.
I already use Spamd with courier-mta and very happy with the combo.

I am not committed to amavis-new. It is just my fist AV MTA integration
and it is the only setup I know.

It is very funny to see the conversation moving from AV question to a
greylist discussion :)



gordan@bobich.net wrote:
> On Wed, 31 Oct 2007, Arturo 'Buanzo' Busleiman wrote:
>
>> gordan@bobich.net wrote:
>>> More to the point, there are many situations where one might send valid
>>> email that would look invalid according to the SPF.

>> Could you provide some examples, please?

>
> Since you asked:
> A consultant comes to my site and needs to send an email out. I run
> transparent port 25 redirection on the firewall to a local smart-host that
> allows sending from the local IPs. This is mainly for logging purposes -
> anybody who has ever had to allow a lot of windows machines on their
> network will have suffered zombies spamming and getting their IP address
> blacklisted as a consequences. With SMTP logs in one place for all
> outbound mail, at least you can identify what internal address it came
> from and thus what machine is/was spamming.
>
> Anyway, the said consultant sends an email from his laptop, and it ends up
> sending from my local, redirected SMTP server. His address would be on a
> domain with an SPF pointing to his network, not mine, yet valid email was
> sent with an SPF record that doesn't match.
>
> Yes, I know this could be worked around using a VPN. But it is an obvious
> example of having to go further out of one's way to work around something
> that was fixed without being broken in the first place. It's not the way
> forward.
>
> Gordan
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> courier-users mailing list
> courier-users@lists.sourceforge.net
> Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 07:13 AM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0