Hi paranoids,
it looks like we have a looping problem on suse-security@suse.com: Someone
with a braindead mail delivery system, most likely a maildrop mailbox
setup, is re-queueing mails delivered via lists.suse.com to
suse-security@ to the recipient in the header.
This means that the mail is being sent back to the list because that
crappy software can't find out that it is supposed to deliver the mail
locally. So if you're seeing mails twice or more times, you know what's
happening.
If you take a closer look at the headers, you will see that some SuSE
email server is one of the hops. That one isn't guilty, it's one of the
following hops. :-)
We have to have an eye on it, trying to eliminate the problem. The header
of the mail doesn't clearly reveal the culprit, so we will have to send
some test mails sooner or later to single subscribers.
Thanks,
Roman.
--
- -
| Roman Drahtmüller
You'll get a mail with the subject "Bounce test, please ignore", please ignore it and don't respond to it. Thanks, -- -ckm
Am Don, 2002-11-07 um 11.28 schrieb Roman Drahtmueller:
Hi paranoids,
it looks like we have a looping problem on suse-security@suse.com: Someone with a braindead mail delivery system, most likely a maildrop mailbox setup, is re-queueing mails delivered via lists.suse.com to suse-security@ to the recipient in the header.
Hello friends (if i still have friends now...),
it was me.
First of all, i stopped my mailserver 'relaying' that way.
What happened:
I installed spamassassin on a SuSE Emailserver 3.1, configured, no,
changed configuration, tested until it SEEMED to work like i wanted.
What happened really:
I made an entry in /etc/procmail/master.cf
smtp inet n - y - - smtpd -o
content_filter=procmail
typed /etc/procmailrc:
:0fw: /tmp/forw.$$
| /usr/bin/spamc
:0: /tmp/spam.$$
* ^X-Spam-Status: Yes
! spam@<private-domain>
:0: /tmp/nospam.$$
! -f "$@"
and everything worked fine...
SPAM was delivered to the spam-account, the remaining mails were
delivered to their destination, until i restarted the mailserver...
there was an amount of ~280 mails stuck in the queue..., most of them CC
or 2nd TO of this list, and some other mailinglist, i fear. this queue
was flushed yesterday evening.
I'm guilty, i know, forgive me, i will never (i hope) do it again.
When procmail forwarded mails to spamc, the original header was lost.
Postfix, receiving the checked mails back, had mails originating from
the local user 'filter' to the recipients mentioned in TO: and CC: and
did, what a good mailserver is intended to do: DELIVER to the
recipients.
I'm really sorry about that,
best regards,
(being ashamed) Erik
complaints to -->
--
Erik Leupold
Hello Erik,
Hi paranoids,
it looks like we have a looping problem on suse-security@suse.com: Someone with a braindead mail delivery system, most likely a maildrop mailbox setup, is re-queueing mails delivered via lists.suse.com to suse-security@ to the recipient in the header.
Hello friends (if i still have friends now...),
it was me. First of all, i stopped my mailserver 'relaying' that way.
I consider it a win for the list that you had the nerve to plead guilty for yourself. I find it very beautiful. And: You saved Chris a lot of work. He was sitting down and sent bounce tests to some thousand subscribers, hoping for the effect to show up. Thank you very much for letting us know! Besides: It could have come worse! :-)
What happened:
I installed spamassassin on a SuSE Emailserver 3.1, configured, no, changed configuration, tested until it SEEMED to work like i wanted.
Make sure you have the perl-MailTools package installed for the case you
turn on the option "-r" in spamassassin. Sebastian had a very good eye on
that one...
Roman.
--
- -
| Roman Drahtmüller
participants (3)
-
Christopher Mahmood -
jader35＠t-online.de -
Roman Drahtmueller