* Drew Tenenholz <dtenenh...@rcn.com>:

> So, in doing all of this analysis, I came accross something odd.  Two Mesages 
> that DID ARRIVE look like this in my /var/log/maillog:
> 
> Mar 31 21:01:31 promedmail postfix/cleanup[32767]: 27A9F758035: 
> message-id=<5158a425.6590700a.0879.ffffb...@mx.google.com>
> Mar 31 21:01:31 promedmail postfix/qmgr[4400]: 27A9F758035: 
> from=<promed-fra-boun...@promedmail.org>, size=14135, nrcpt=311 (queue active)
> ...
> Mar 31 21:01:32 promedmail postfix/smtp[307]: 27A9F758035: 
> to=<pollac...@mindspring.com>, relay=tummms.chboston.org[134.174.12.42]:25, 
> delay=1.2, delays=0.73/0.07/0.04/0.37, dsn=2.0.0, status=sent (250 2.0.0 
> 1ayt400cs0-1 Message accepted for delivery)
> 
> and
> 
> Apr  2 02:29:52 promedmail postfix/cleanup[6635]: 54981758035: 
> message-id=<515a428b.50...@gmail.com>
> Apr  2 02:29:52 promedmail postfix/qmgr[4400]: 54981758035: 
> from=<promed-eafr-boun...@promedmail.org>, size=8554, nrcpt=480 (queue active)
> ...
> Apr  2 02:29:52 promedmail postfix/qmgr[4400]: 54981758035: 
> from=<promed-eafr-boun...@promedmail.org>, size=8554, nrcpt=480 (queue active)
> 
> 
> while messages that DID NOT ARRIVE all sort of look like this:
> 
> Mar 30 04:00:35 promedmail postfix/cleanup[18138]: ACCE0758034: 
> message-id=<201303300400.r2u402tx030...@healthmap.chip.org>
> Mar 30 04:00:35 promedmail postfix/qmgr[4400]: ACCE0758034: 
> from=<promed-daily-update-boun...@promedmail.org>, size=9316, nrcpt=500 
> (queue active)
> ...
> Mar 30 04:00:36 promedmail postfix/smtp[18143]: ACCE0758034: 
> to=<pollac...@mindspring.com>, relay=tummms.chboston.org[134.174.12.42]:25, 
> conn_use=8, delay=2.1, delays=1.1/0.46/0/0.55, dsn=2.0.0, status=sent (250 
> 2.0.0 1b42w6x590-8 Message accepted for delivery)
> 
> 
> OK, if you've gotten this far, you'll see that the message-id ends in either 
> mx.google.com or gmail.com (which are popular and common, and go through) and 
> failing messages end in my specialized domain healthmap.chip.org.  Is this 
> the sort of thing that causes a problem with delivery?  Are we maybe missing 
> some sort of PTR records in the DNS?  That is fixable, but I don't understand 
> why some messages get the 'special' domain and others do not.

Have you tried enabling VERP? So there's one message per recipient.

-- 
Ralf Hildebrandt                   Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.de        Campus Benjamin Franklin
http://www.charite.de              Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Reply via email to