Re: [exim] Wondering if this is possible?

On Thu, Aug 23, 2007 at 07:00:25PM -0400, [EMAIL PROTECTED] wrote: > It appears I have someone exploiting a form on a clients website. The > problem is the site is massive and they have multiple forms. The email > also appears to be valid as email is being sent to it. I'm a little unclear as to wh

[exim] Wondering if this is possible?

It appears I have someone exploiting a form on a clients website. The problem is the site is massive and they have multiple forms. The email also appears to be valid as email is being sent to it. I can get the message id numbers but since they are delivered I can't view them because nothing is stor

Re: [exim] Interesting log entry

Jeroen van Aart wrote: > Hello, > > I noticed this log entry, which I have not seen before: > > 2007-08-23 11:17:49 SMTP protocol synchronization error (next input sent > too soon: pipelining was not advertised): rejected "Subject:¡erelay > ok¡f66.252.xxx.xxx" H=219-84-61-136-adsl-tpe.dynamic.s

Re: [exim] Interesting log entry

Jeroen van Aart wrote: > Hello, > > I noticed this log entry, which I have not seen before: > > 2007-08-23 11:17:49 SMTP protocol synchronization error (next input sent > too soon: pipelining was not advertised): rejected "Subject:¡erelay > ok¡f66.252.xxx.xxx" H=219-84-61-136-adsl-tpe.dynamic.s

Re: [exim] Exim 4.67 - how to force usage of a specific authenticator when acting as a client

Hello Philip, > The forthcoming Exim 4.68 (which I hope to release early in September if > not before - meanwhile you can use the snapshot if you want) contains > this new feature: thank you for this information. I'll try it out. Regards Jürgen -- Mail: [EMAIL PROTECTED] GPG Key available --

[exim] Interesting log entry

Hello, I noticed this log entry, which I have not seen before: 2007-08-23 11:17:49 SMTP protocol synchronization error (next input sent too soon: pipelining was not advertised): rejected "Subject:¡erelay ok¡f66.252.xxx.xxx" H=219-84-61-136-adsl-tpe.dynamic.so-net.net.tw [219.84.61.136] next in

Re: [exim] Header syntax checking

Magnus Holmgren wrote: > A considerable number of list subscribers' mail servers rejected today's two > postings from "tao", complaining about the mail header not being RFC 2822 > compliant. Apparently the error was that the To: field > contained "[EMAIL PROTECTED]" (note the explicit root doma

Re: [exim] Fake ACCEPT (ahem)

Here's a little bit of a modification to the traditional way to use ClamAV to give more meaningful rejection messages warnmalware = */defer_ok set acl_c_clam_message = ${lc:$malware_name} dropcondition = ${if match{$acl_c_clam_message}{trojan|worm}{true}{false}} message

[exim] Header syntax checking

A considerable number of list subscribers' mail servers rejected today's two postings from "tao", complaining about the mail header not being RFC 2822 compliant. Apparently the error was that the To: field contained "[EMAIL PROTECTED]" (note the explicit root domain final dot). Indeed this is

Re: [exim] Accept emails coming from a particular IP for a particular domain

Madan Thapa wrote: > First of all thank you for your support. > > Let me explain my case in more detail.. > > I have 5 domains on a server.. > > domain1 > domain2 > domain3 > domain4 > domain5 > > domain2 to domain5 should be able to recieve emails from anyone. But > domain1 should r

Re: [exim] Accept emails coming from a particular IP for a particular domain

Hello, First of all thank you for your support. Let me explain my case in more detail.. I have 5 domains on a server.. domain1 domain2 domain3 domain4 domain5 domain2 to domain5 should be able to recieve emails from anyone. But domain1 should recieve email from only 1 IP(s) or hos

Re: [exim] extract in string expansion

On Thu, Aug 23, 2007 at 04:31:36PM +0200, [EMAIL PROTECTED] wrote: > > ${extract{result}{result=clean reason=spamtrap}} > clean > > > ${extract{result}{result=clean reason="abc def"} > Failed: missing or misplaced { or } Well, don't miss off the final } then :-): > ${extract{result}{result=c

[exim] extract in string expansion

Hello everyone, I'd like to use extract with keys, as it makes for more readable config than extract with number/string separator. Sadly, I have trouble to get former to work with double quotes: da7 (87.204.147.157) ~ % exim -be > ${extract{result}{result=clean reason=spamtrap}} clean > ${extrac

Re: [exim] Accept emails coming from a particular IP for a particular domain

On Thu, Aug 23, 2007 at 07:34:37PM +0530, Madan Thapa wrote: > Is there any way to configure exim to reject all mail to a server say > (ServerA) for a particular domain say xyz.com, unless it comes from a > certain IP(s) , while still allowing the other domains on the server accept > mail from anyo

Re: [exim] Accept emails coming from a particular IP for a particular domain

Mike Cardwell wrote: >> Is there any way to configure exim to reject all mail to a server say >> (ServerA) for a particular domain say xyz.com, unless it comes from a >> certain IP(s) , while still allowing the other domains on the server >> accept >> mail from anyone? > > In the rcpt acl: > >

Re: [exim] Accept emails coming from a particular IP for a particular domain

Madan Thapa wrote: > Is there any way to configure exim to reject all mail to a server say > (ServerA) for a particular domain say xyz.com, unless it comes from a > certain IP(s) , while still allowing the other domains on the server accept > mail from anyone? In the rcpt acl: deny domain = exa

[exim] Accept emails coming from a particular IP for a particular domain

Hello, Is there any way to configure exim to reject all mail to a server say (ServerA) for a particular domain say xyz.com, unless it comes from a certain IP(s) , while still allowing the other domains on the server accept mail from anyone? Thanks -- ## List details at http://lists.exim.org/ma

Re: [exim] Fake ACCEPT (ahem)

Michael Sprague wrote: > On Thu, Aug 23, 2007 at 11:56:20AM +0100, Mike Cardwell wrote: > >> Marcin Krol wrote: >> >> >> But why would you want to accept and silently discard mail? If the mail >> contains a virus, don't you think it's better that the sender is told so? >>

Re: [exim] Fake ACCEPT (ahem)

On Thu, Aug 23, 2007 at 11:56:20AM +0100, Mike Cardwell wrote: > Marcin Krol wrote: > > But why would you want to accept and silently discard mail? If the mail > contains a virus, don't you think it's better that the sender is told so? > > >>> No! That causes collateral spam

Re: [exim] Fake ACCEPT (ahem)

Marcin Krol wrote: > John Hall pisze: > But why would you want to accept and silently discard mail? If the mail contains a virus, don't you think it's better that the sender is told so? >>> No! That causes collateral spam! Think faked sender... >>> >>

[exim] Date: header in non-english format

Hi! I'm receiving bounce messages from my Exim server with Date: header in spanish language, something like this: Date: jue, 23 ago 2007 14:35:06 +0200 Only bounce messages have Date header: in spanish. All another cases have Date: header in english. Server's locales are this: [EMAIL PROTECTED]

Re: [exim] Fake ACCEPT (ahem)

Marcin Krol wrote: > Hello, > > OK, so as some of you may know, clamav now features filtering out > phishing and/or spam as well. > > The problem is this generates rather unreadable reject messages: > > SMTP error from remote mail server after end of data: > host mail.da4.promo.pl [83.149

Re: [exim] SPAM with empty subject field

[EMAIL PROTECTED] wrote: >>> My search of the pdf file found mention of the $h_subject variable. >>> >>> Is this variable available in Exim? >> $h_HEADERNAME: contain the various headers and is case insensitive. >> Eg: $h_subject: and $h_SUBJECT: and $h_Subject: all equal the same >> thing. >

Re: [exim] SPAM with empty subject field

On Thu, Aug 23, 2007 at 01:33:22PM +0100, [EMAIL PROTECTED] wrote: > I have searched the v4.6x spec pdf file for $h_HEADERNAME but it wasn't > found. Where is this all documented? http://www.exim.org/exim-html-current/doc/html/spec_html/index.html#toc0140 Search for "$rheader_". > Before you repl

Re: [exim] SPAM with empty subject field

>> My search of the pdf file found mention of the $h_subject variable. >> >> Is this variable available in Exim? > > $h_HEADERNAME: contain the various headers and is case insensitive. > Eg: $h_subject: and $h_SUBJECT: and $h_Subject: all equal the same > thing. I have searched the v4.6x spec

Re: [exim] Fake ACCEPT (ahem)

On Thu, Aug 23, 2007 at 01:07:25PM +0200, Marcin Krol wrote: > Dave Evans pisze: > > This is fine, but ONLY if you send the message to the correct person, which > > is > > usually NOT <$sender_address>. Alas in most environments you won't know who > > to send it to! > > > > Do NOT automatically s

Re: [exim] SPAM with empty subject field

[EMAIL PROTECTED] wrote: > Lately we have been receiving a lot of SPAM with the empty subject > field. > > I have searched the Exim 4 book and also the v4.6x spec pdf file looking > for a variable that holds an incoming message's subject as I want to do > a check in the acl_smtp_data ACL for thi

Re: [exim] Fake ACCEPT (ahem)

Dave Evans pisze: > This is fine, but ONLY if you send the message to the correct person, which is > usually NOT <$sender_address>. Alas in most environments you won't know who > to send it to! > > Do NOT automatically send messages to <$sender_address>! Well of course that would generate mostly

[exim] SPAM with empty subject field

Lately we have been receiving a lot of SPAM with the empty subject field. I have searched the Exim 4 book and also the v4.6x spec pdf file looking for a variable that holds an incoming message's subject as I want to do a check in the acl_smtp_data ACL for this type of SPAM. Is there such a vari

Re: [exim] Fake ACCEPT (ahem)

Marcin Krol wrote: But why would you want to accept and silently discard mail? If the mail contains a virus, don't you think it's better that the sender is told so? >>> No! That causes collateral spam! Think faked sender... >>> >> Not if you're rejecting during the SMT

Re: [exim] Fake ACCEPT (ahem)

On Thu, Aug 23, 2007 at 12:37:57PM +0200, Marcin Krol wrote: > > Not if you're rejecting during the SMTP transaction, which is I think > > what was being discussed originally. > > > Correct, *but the default clamav message saying so is unreadable*. > > So I need to blackhole the message myself

Re: [exim] host_lookup = *

- Original Message - From: "ROGERS Richard" <[EMAIL PROTECTED]> To: "Phil (Medway Hosting)" <[EMAIL PROTECTED]>; "Exim Users List" Sent: Thursday, August 23, 2007 10:56 AM Subject: RE: [exim] host_lookup = * > I think you nmay have been lucky - there are certainly some out there. > Th

Re: [exim] Fake ACCEPT (ahem)

John Hall pisze: >>> But why would you want to accept and silently discard mail? If the mail >>> contains a virus, don't you think it's better that the sender is told so? >>> >> No! That causes collateral spam! Think faked sender... >> > > Not if you're rejecting during the SMTP trans

Re: [exim] Fake ACCEPT (ahem)

Mike Cardwell wrote: > What the original author of this thread is looking for here is > fakereject. If you do this: > > "accept control = fakereject" > > Then the message will look to the sender as though it has been accepted, > but instead of hitting the routers it will just disappear into a

Re: [exim] Fake ACCEPT (ahem)

Jan-Piet Mens wrote: >> But why would you want to accept and silently discard mail? If the mail >> contains a virus, don't you think it's better that the sender is told so? > No! That causes collateral spam! Think faked sender... No it doesn't. Not if you reject during SMTP. Collateral spam is

Re: [exim] Fake ACCEPT (ahem)

On 23/08/07, Jan-Piet Mens <[EMAIL PROTECTED]> wrote: > > But why would you want to accept and silently discard mail? If the mail > > contains a virus, don't you think it's better that the sender is told so? > > No! That causes collateral spam! Think faked sender... Not if you're rejecting duri

Re: [exim] Fake ACCEPT (ahem)

On Thu, Aug 23, 2007 at 11:52:27AM +0200, Jan-Piet Mens wrote: > On Thu Aug 23 2007 at 11:47:17 CEST, Dave Evans wrote: > > > But why would you want to accept and silently discard mail? If the mail > > contains a virus, don't you think it's better that the sender is told so? > > No! That causes

Re: [exim] host_lookup = *

Phil (Medway Hosting) wrote: > I have been rejecting ALL connections with no rDNS for at least 6 > months. Not a single false positive reported - yet. > > All the best > > Phil I think you nmay have been lucky - there are certainly some out there. This one (brought to my attention the other day)

Re: [exim] Fake ACCEPT (ahem)

On Thu Aug 23 2007 at 11:47:17 CEST, Dave Evans wrote: > But why would you want to accept and silently discard mail? If the mail > contains a virus, don't you think it's better that the sender is told so? No! That causes collateral spam! Think faked sender... -JP -- ## List details

Re: [exim] Fake ACCEPT (ahem)

On Thu, Aug 23, 2007 at 11:35:40AM +0200, Marcin Krol wrote: > Hello, > > OK, so as some of you may know, clamav now features filtering out > phishing and/or spam as well. > > The problem is this generates rather unreadable reject messages: > > SMTP error from remote mail server after end of

[exim] Fake ACCEPT (ahem)

Hello, OK, so as some of you may know, clamav now features filtering out phishing and/or spam as well. The problem is this generates rather unreadable reject messages: SMTP error from remote mail server after end of data: host mail.da4.promo.pl [83.149.102.11]: 550 Wirus (virus): Ema

Re: [exim] Piping message in ACL DATA

Hi !! > Is there any way (outside standard connection to SA via > "malware" condition) to pipe message into $run in acl_data? Smth > like that would definitely make Exim shine (even more, that is :-)... try this (example has been updated): http://www.ols.es/exim/dlext -- Best regards ...

Re: [exim] Controlling relaying by checking local_part?

On Thu, Aug 23, 2007 at 10:27:32AM +0200, Sbs Bofh wrote: > There are now many thousands of orphaned mailboxes in the format > /vmail//zzzoidofiahsc caused by spam and bounces so this > behaviour has got to stop :-) I'm not sure what you mean by "orphaned" in that context. Are the mailboxes f

[exim] give me advice for account issue

im using Exim 4.63 on debian etch. im setting up exim on the system required some virtual domains, and i have to set up this system with next requirements. 1. accounts having same localpart and different domainpart is completely different account. for example, [EMAIL PROTECT

Re: [exim] how to specify new line as list separator?

thanks Magnus. > It's \n, not /n, and that feature wasn't added until version 4.67. oh, yes, i've mistaken when i wrote that.. anyway, i could solve this problem with using this domainlist. domainlist local_domains = ldap;ldap::///ou=DomainZone,dc=example,dc=net?dnszonename?sub?(&(objectClass=d

Re: [exim] Piping message in ACL DATA

On Wed, 22 Aug 2007, [EMAIL PROTECTED] wrote: > Is there any way (outside standard connection to SA via > "malware" condition) to pipe message into $run in acl_data? Smth > like that would definitely make Exim shine (even more, that is :-)... As Magnus pointed out, this is not directly available,

[exim] Controlling relaying by checking local_part?

I have inherited the task of looking after two servers which run exim, essentially set up as a front-end/back-end pair. The front end server is accessible from the outside world, is published as the MX for the domain, and relays mail to the backend server using a "driver = manualroute" router. Th