Re: [exim] SPAM Filtering - Losing the war!

s - I ran into it myself when trying to E-mail an HTML file without an extension (it was named simply somedomain.com). Cheers, -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserver.com -- ## List details at http://www.exim.org/mailman/listinfo/exi

Re: [exim] Mail from the future...

UTC so without knowing the timezone, figured it was 9 hours off. -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserver.com -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wik

Re: [exim] Forbid HELO

On Thursday 26 October 2006 01:57, W B Hacker wrote: > and, of course, the 'general case' - that of using, instead of port 25, > port 24 - which was set aside for that purpose [1] long ago - so as to > segregate such traffic from the 'rest of' the smtp arrivals. s/24

Re: [exim] Exim has a bad queue handling?

onsider for that is for supporting remote TLS hosts. Cheers, -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserver.com -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/

Re: [exim] Exim has a bad queue handling?

still for the MSA (accept authenticated connections from client), but then use qmail to route all outbound E-mail, both from our servers as well as the MSA. But that's an ideal I live without for now. Cheers, -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] -

Re: [exim] Converting from Qmail to Exim

tem. You really want to use maildir instead of whatever you're calling "exim mailfile format" (probably mbox I guess). It has numerous advantages. -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserver.com -- ## List details at http://w

Re: [exim] per user spamassassin setup

he router or whatever exim hands the mail off to (maildrop, for instance). You can use the ACL variable in the routers. Cheers, -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserver.com -- ## List details at http://www.exim.org/mailman/listinfo/e

Re: [exim] Really Cool Trick

oach, and fixing them requires more filtering work than without. Cheers, -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserver.com -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/

Re: [exim] conducive.org

, which I did not do. I did not send a wishlist request to the dev list at all, and further, I'm not even the one who requested the feature in the first place. -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserver.com -- ## List details at http://www.

Re: [exim] conducive.org

that this entire thread is? I find it a bit ironic to see a huge discussion of problems with somebody's personal MTA when that same somebody objected so to my small handful of E-mails discussing a potential feature that is of interest to everyone. -- SeattleServer.com Mailing Lists - Casey A

Re: [exim] auto-replies, forwards and such

ECTED] : \ ! [EMAIL PROTECTED] : \ ! [EMAIL PROTECTED] transport = vacation_autoresponse unseen no_verify no_expn Cheers, -- SeattleServer.com Mailing Lists - Casey Allen Shobe [E

Re: [exim] Adding a per-recipient message header

thing to do with the tasks at hand then? That is all, thanks, -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserver.com -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wik

Re: [exim] ACL Question

host disconnects prior to RCPT. -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserver.com -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/

Re: [exim] Adding a per-recipient message header

7;re responding to here, and that was only intended to put a few smiles on faces, not to offend anyone. I did appreciate the advice given - as another said, one sometimes simply has to use the tools available. Cheers, -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL

[exim] SPF variable issues / quote_url request

lists%40seattleserver.com&ip=64.81.164.204&receiver=a.mx.seattleserver.com Cheers, -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserver.com -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/

Re: [exim] Adding a per-recipient message header

}? Will there be functions to escape/unescape things?) Again, hashes seem cleaner as they would (probably, this is an assumption) not have to be as restricted. Cheers, -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserver.com -- ## List details a

Re: [exim] Adding a per-recipient message header

though, thanks for the workaround idea. :) I must say I'd quite like to see those hash functions though... Cheers, -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserver.com -- ## List details at http://www.exim.org/mailman/listinfo/exim-users

Re: [exim] Timeout with spamassassin

the users having to dig through a pile of spam all the time anyways, which in my book, defeats the whole purpose of filtering it in the first place. Bayesian - neat theory, bad reality. Now, what am I supposed to do with all these 15kRPM SCSI disks? ;-) Cheers, -- SeattleServer.com Mailing

Re: [exim] Adding a per-recipient message header

to know a more correct solution... > This problem wouldn't exist if there were some inbuilt functions for > working with hash style acl variables, other than extracting from > them. Agreed. I'd love to see that in future exim versions... -- SeattleServer.com Mailing

Re: [exim] Adding a per-recipient message header

arnset acl_m4 = ${lookup pgsql{select "statistics_record_message_recipient" (${quote_pgsql:${acl_m6}}, '${quote_pgsql:[EMAIL PROTECTED]')} {${value}}fail} set acl_m10 = [EMAIL PROTECTED] ${acl_m10} [...] maildrop: [...] headers_add

Re: [exim] How can I get rid of 58.69.173.42

60s log_message = No reverse DNS record present for ${sender_host_address} (claimed to be ${sender_helo_name}). Cheers, -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserver.com -- ## List details at h

Re: [exim] Adding a per-recipient message header

oesn't? Cheers, -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserver.com -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/

Re: [exim] Adding a per-recipient message header

On Saturday 14 October 2006 04:28, John Robinson wrote: > On 14/10/2006 10:17, SeattleServer.com wrote: > > Somebody mentioned using a router to add per-recipient headers, but I > > don't see how this would work as acl_m4 is set at rcpt acl time. > > I'm guessing

[exim] Adding a per-recipient message header

-recipient headers, but I don't see how this would work as acl_m4 is set at rcpt acl time. Suggestions? (Please CC me on any responses - I seem to be having some issues getting list posts...) Cheers, -- SeattleServer.com Mailing Lists - Casey Allen Shobe [EMAIL PROTECTED] - http://seattleserv