Re: .mailfilter rule mysteriously not followed
Sam Varshavchik <[email protected]>
| Newsgroups | gmane.mail.maildrop |
|---|---|
| Message-ID | <[email protected]> |
Dr Michael Daly writes: > Funnily enough, there's no entry at all in maildrop's log for these > anomalous mail deliveries from my Dallas based server...the only maildrop > log entries I find relate to mail delivered from Internode. It seems to > suggest maildrop is being bypassed for mail from Dallas? Correct. Just because maildrop is installed on a server, doesn't mean that all mail will automatically, and magically, be delivered by maildrop. It is necessary to explicitly configure whatever handles incoming mail, namely your mail server, to have it hand off mail to be delivered by maildrop. It's possible that if you're installing a pre-built package that someone else made, that the package takes care of it. But, if you are building and instlaling maildrop yourself, that's going to be your job to do that. There is not standard and uniform way that every mail server in the world gets configured. Every one of them is different. maildrop's installation script does not attempt to figure out what mail server is installed on the server, and how to configure it. That's something that needs to be done by hand. > Using the -V > option for maildrop does not seem to help - I understand that Verbose mode > does not work when maildrop runs in delivery mode? Correct. But you can simply save an email message in a file, and run maildrop from the command line, passing the email message on standard input, with the -V option, to see what maildrop will do with it. But that assumes that maildrop actually gets used to deliver the mail, and you are suggesting that it's not, so this point is moot. > This is the fetchmail log for a message received by [email protected] > (as sent from Internode, as it happens): > > fetchmail: Trying to connect to 127.0.0.1/25...connected. > fetchmail: SMTP> MAIL FROM:<[email protected]> SIZE=1357 > fetchmail: SMTP< 250 2.1.0 Ok > fetchmail: SMTP> RCPT TO:<mdtest5@localhost> This shows that fetchmail, after downloading your message, connected to your mail server on port 25, and dumped the message on your mail server, addressing it to <mdtest5@localhost>. There's no evidence here that maildrop gets invoked, in any way. Presumably your mail server will take the message, and invoke maildrop to deliver it. But, that's not shown here. Furthermore, your other message, that claims that it gets delivered correctly, indicates, in its headers, that it was delivered to "mdtesting", not "mdtest5". > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > finally, /opt/etc/fetchmailrc has: > poll mydomain.com.au service 110 protocol pop3 uidl > user "lists" password "XXXXXX" is "mdtesting" here > > poll mail.internode.on.net service 110 protocol pop3 uidl > user "michaeldaly" password "XXXXXX" is "mdtesting" here > > > Anyway...anyadvice would be helpful! I don't know anything much about fetchmail, I don't use it, but I do not see "mdtest5" mentioned anywhere here, so it beats me where fetchmail got it from. Furthermore, again, the big missing piece here is how maildrop is involved at all, since I don't see anything that suggests that maildrop gets used for local mail delivery. ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Courier-maildrop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/courier-maildrop
signature.asc
(application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) iEYEABECAAYFAlEErjUACgkQx9p3GYHlUOKXXQCfY9a8vr6d7Kbm4MbNxaomwFT1 rjkAniW9xwh6YaziZZQNbyBokoNaAeVr =PDPy -----END PGP SIGNATURE-----