[xmail] Re: Drop NDRs?
This would be something that I would like to be able to do as well, as at times we can bet a mass of dictionary mails sent to us. There are two ways I can think to do this: 1) Possibly edit the SMAILProcessFile (I think thats where it gets processed) function in SMAILSvr.cpp and make that drop the file? But I am not sure if this is the best approach, this would require help from someone that has a much better understanding of the source? 2) I think this should also be achievable by putting a filter on the domains to control in this fashion. I have never used the filters option in xmail and am unsure where would be best to put the filter, as there are many possible places in the delivery chain it can go. Option 1 would be the fastest as it would be compiled, but option 2 would be easier to implement. Is this something that anyone else out there has done before? Dale Qualls wrote: I've got an xmail box acting as a secondary MX and a custdomain simply re-directing the mail to our primary MX. Whenever there is a non-deliverable (dictionary attack), the secondary sends an NDR to the spammer address and then has to accept a NDR back when the receiving spoofed server sends it. Is there a way to drop the NDRs when they come back? Also, my spool is loaded with messages that xmail keeps trying to deliver to obviously bad addresses. I don't want to set a low timeout threshold in case the primary MX is down for an extended period of time as this would cause legitimate messages to get dumped. Any thoughts?? TIA! - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Drop NDRs?
Thanks for the reply, it sounds like both would be good options. I too am interested to see if anyone else has done this and can offer any guidance. Cripes, my spool has so many messages that Harald's XQMWIN can't seem to load them all and just hangs. I hate to simply clear the spool for fear that something important might get dropped. Thank you Vinny Wadding wrote: This would be something that I would like to be able to do as well, as at times we can bet a mass of dictionary mails sent to us. There are two ways I can think to do this: 1) Possibly edit the SMAILProcessFile (I think thats where it gets processed) function in SMAILSvr.cpp and make that drop the file? But I am not sure if this is the best approach, this would require help from someone that has a much better understanding of the source? 2) I think this should also be achievable by putting a filter on the domains to control in this fashion. I have never used the filters option in xmail and am unsure where would be best to put the filter, as there are many possible places in the delivery chain it can go. Option 1 would be the fastest as it would be compiled, but option 2 would be easier to implement. Is this something that anyone else out there has done before? Dale Qualls wrote: I've got an xmail box acting as a secondary MX and a custdomain simply re-directing the mail to our primary MX. Whenever there is a non-deliverable (dictionary attack), the secondary sends an NDR to the spammer address and then has to accept a NDR back when the receiving spoofed server sends it. Is there a way to drop the NDRs when they come back? Also, my spool is loaded with messages that xmail keeps trying to deliver to obviously bad addresses. I don't want to set a low timeout threshold in case the primary MX is down for an extended period of time as this would cause legitimate messages to get dumped. Any thoughts?? TIA! - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Drop NDRs?
At 23.43 05/03/07, you wrote: Also, my spool is loaded with messages that xmail keeps trying to deliver to obviously bad addresses. This has been mostly cured with XMail = 1.23. Which version are you running? Ciao, Francesco - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Drop NDRs?
I am not 100% if my issue is the same as Dale's. But I am currently running XMail 1.23 and when I look at my spool queue I see lots of bounce messages trying to be sent to people as the result from dictionary spam attacks etc. [00] XMail bounce: [EMAIL PROTECTED];Error=[Unknown user Username in domain OneOfMyLocal.Domains] What would solve my problem (and possibly dale's as well) would be to just throw away the message if the user doesn't exist. Don't send a bounce back or try to process it any further. Is that possible? Francesco Vertova wrote: At 23.43 05/03/07, you wrote: Also, my spool is loaded with messages that xmail keeps trying to deliver to obviously bad addresses. This has been mostly cured with XMail = 1.23. Which version are you running? Ciao, Francesco - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Drop NDRs?
Hmmm, I'm running 1.23. Francesco Vertova wrote: At 23.43 05/03/07, you wrote: Also, my spool is loaded with messages that xmail keeps trying to deliver to obviously bad addresses. This has been mostly cured with XMail = 1.23. Which version are you running? Ciao, Francesco - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Drop NDRs?
On Mon, 5 Mar 2007, Dale Qualls wrote: I've got an xmail box acting as a secondary MX and a custdomain simply re-directing the mail to our primary MX. Whenever there is a non-deliverable (dictionary attack), the secondary sends an NDR to the spammer address and then has to accept a NDR back when the receiving spoofed server sends it. Is there a way to drop the NDRs when they come back? Also, my spool is loaded with messages that xmail keeps trying to deliver to obviously bad addresses. I don't want to set a low timeout threshold in case the primary MX is down for an extended period of time as this would cause legitimate messages to get dumped. Any thoughts?? From XMail 1.23 ahead, if the target domain does not exist, you get a bounce immediately. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: SMTP-TLS bug?
- Original Message - From: Davide Libenzi davidel@xmailserver.org To: xmail@xmailserver.org Sent: Tuesday, March 06, 2007 4:49 PM Subject: [xmail] Re: SMTP-TLS bug? On Mon, 5 Mar 2007, Ivo Smits wrote: THat seems ok. How is your AllowNullSender set? I already checked that: AllowNullSender 1 Can you check if this is really associated with Exim trying to send? AUTH=EFAIL:TYPE=LOGIN - Davide When using tail -f on XMail's SMTP log the message comes in right after I execute 'echo bla | sendmail ivo' on the system running exim. (note that it IS working with TLS disabled, so it isn't in the email address or message). The log entries also show the IP of the machine running Exim (192.168.1.2, the machines are connected using an OpenVPN tunnel...): UFO-Net.nlUFO-Net.nl192.168.1.2 2007-03-06 17:02:41 localhost.localdomain AUTH=EFAIL:TYPE=LOGIN 0 UFO-Net.nlUFO-Net.nl192.168.1.2 2007-03-06 17:02:42 localhost.localdomain AUTH=EFAIL:TYPE=LOGIN 0 - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Receiving Mail multiple times
It's a tough problem to track down, but the fact that it happens on the web client as well as in Outlook leads me to believe that it's not a multiple-click problem (with the user attempting to connect to the POP3 server multiple times.) When I say ALL 5 twice that's exactly it...they click Check Mail once, and they might receive the next few messages, but each of the new ones will appear twice in their inbox. Aaron On 3/6/07, CLEMENT Francis [EMAIL PROTECTED] wrote: This problem is generaly caused by a time out in the pop3 session and = as many pop3 clients delete messages after retrieving all of them (not = after retreiving each, for historical reasons); if session drop for any = reason, then next time the pop3 client retreive all the mails. Main causes for time out are, combined or not, from most common to less common : - Client Anti-virus software : some are 'specialists' to break pop3 = sessions on slow links with large mails (or not), or with no rfc compliant mails (some spams) - Client computer busy - Client connexion busy (especially when sharing the connexion) - Bad mail that can cause some mua to hang - Server busy or Server side connexion congestion When you say they will receive ALL 5 twice, do you mean that they = receive twice after ONLY ONE click on check mail without any error ? Francis -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Aaron Fransen Envoy=E9 : lundi 5 mars 2007 23:51 =C0 : xmail@xmailserver.org Objet : [xmail] Receiving Mail multiple times We have some 700 users being served by XMail on a fairly peppy IBM xSeries server (dual Xeon, 4GB ram, fibre-channel SAN disk) through clients like Outlook Express and Outlook, and our own home-grown web-based mail client. Occasionally users will report that they receive the same emails twice (or thrice even!). For example, if it's going to happen, when the user clicks check mail and there are five emails sitting there for them, they will receive ALL 5 twice (total of 10), not just one or two of them. The header information on the emails is identical, and it appears to affect all client types. Has anyone seen anything like this before? (I should note that it seems to be more of a problem with the server becomes somewhat burdened by the MySQL server running the web client...) Thanks! - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Drop NDRs?
But is there anyway to dump them? What if I (against the RFC) get rid of the postmaster account, will they just get dropped and not fill up the spool? Davide Libenzi wrote: On Mon, 5 Mar 2007, Dale Qualls wrote: I've got an xmail box acting as a secondary MX and a custdomain simply re-directing the mail to our primary MX. Whenever there is a non-deliverable (dictionary attack), the secondary sends an NDR to the spammer address and then has to accept a NDR back when the receiving spoofed server sends it. Is there a way to drop the NDRs when they come back? Also, my spool is loaded with messages that xmail keeps trying to deliver to obviously bad addresses. I don't want to set a low timeout threshold in case the primary MX is down for an extended period of time as this would cause legitimate messages to get dumped. Any thoughts?? From XMail 1.23 ahead, if the target domain does not exist, you get a bounce immediately. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
