http://lists.datasmuggler.com/listinfo.cgi/dhprocmailusers-datasmuggler.com

“It looks like that our system will not allow messages sent from ebay,
paypal to be resent because our system shows that the message can be
considered “phishing”.

We have specific restrictions such as this to prevent phishing scams.

I would suggest setting up a new email address for paypal and ebay and
don’t forward that address to the shell just add a separate filter from
the panel to discard everything that doesn’t come from Ebay/Paypal.

Or, you can even add a new filter that comes before the forward to shell
and that would send any ebay/paypal messages to another folder and select
the “execute and stop” for that filter.”

I’m not giving up yet…

My response:

It looks like that our system will not allow messages sent from ebay,
paypal to be resent because our system shows that the message can be
considered “phishing”.

We have specific restrictions such as this to prevent phishing scams.

I would suggest setting up a new email address for paypal and ebay and
don’t forward that address to the shell just add a separate filter from
the panel to discard everything that doesn’t come from Ebay/Paypal.

Or, you can even add a new filter that comes before the forward to shell
and that would send any ebay/paypal messages to another folder and select
the “execute and stop” for that filter.

I just ran into this issue too. I WAS getting emails from ebay until 12/4, however I am not getting these now. I’m now getting bounces for anything sent from ebay when I try to procmail and forward. This is seriously getting out of control. I am month to month now so I may just have to bail. DH you need to fix this.

Dan

The procmail install on the user machines blocks forwarding for large institutional domain names, such as paypal, ebay, schwab, etc. This is done to prevent phisers from using Dreamhost to solicit information. However, it has the very unfortunate side effect of bouncing all mail from these sites.

I have been haggling with dreamhost for weeks and they just finally figured it out and set me this response:

—–

Hello,

I’m a little surprised that Andrea missed this, the problem here, is that you have “ebay” in a “from” header. The server then responds:

Error: No mail with this sender address allowed (in reply to end of DATA command)

Basically, we have a pretty blunt instrument on the web server side, that blocks mail with any “from” headers that contain known domains like “ebay”, “paypal”, “bankofamerica”, stuff like that.

Since we’re now asking users to send through the web servers, we may need to look into lifting those restrictions, however, that’s what’s happening at this time, and why you’re getting that bounce.

Again, I’ll bring this to the attention of our administration, but for now, we can’t remove that restriction without review.

Sorry about that!

Thanks!
Brian H

——-

Well thanks Brian for telling me. But hey could you be a little more cavalier about bouncing what is essentially my most important emails. (sarcasm)

So what I did in the mean time is to setup the following procmail filter:

:0
* ^From: MAILER-DAEMON@olds.dreamhost.com
$HOME/Maildir/

And then offlineimap syncs these emails over eventually. So much for instant email.

This is obviously less than ideal. And I hope Dreamhost fixes this ASAP. I suggested they look into allowing forwarding of these domains to DH servers only. This would still provide protection while allowing procmail to function.

Ugh, thanks DH for dropping the ball . . . again.(also sarcasm)

@STEREO The new servers perform better due to less random stuff running on them as well as better performance from the data storage due to less resource contention from other servers (ie the web servers).

One thing worth pointing out is that users might want to avoid setups with excessive forwarding between mail accounts. Dreamhost have an SMTP quota that allows no more than 100 emails / hour. If users are not careful, it is easy to end up doing more than 100 forwards an hour, with a bounce loop as result. The smtp server will reject the 101th email going back to your spam_checker_passed@ and send it back to the spam_checker@ account which in turn tries to forward the bounce to spam_checker_passed@, creating a loop.

To break such forwarding loops, users might want to add an X-Loop header before the email forward in .procmailrc. In my case, I added this recipe to .procmailrc just before the forward to spam_checker_passed@.

:0fw
| formail -A “X-Loop: loop_alert@liljeqvist.com”

I search all incoming emails for that X-Loop header to detect and break any loops. Here is one of my first procmail recipes:

# If we find an X-loop, then it is a bounce.
:0
* ^X-Loop: loop_alert@liljeqvist.com
$MAILDIR/.LoopProblems/

I want to create backups of all emails but do not want to forward the backup copies to my main account. Instead I create a backup copy of each email in a folder called ShortTermArchive. I then sync this to my mail server using offlineimap. I also want to copy any bounce emails across, so must therefore sync several folders using offlineimap. To synchronise more than one folder, write something like this in .offlineimaprc:

folderfilter = lambda foldername: foldername in ['INBOX.ProbablySpam','INBOX.ShortTermArchive','INBOX.LoopProblems']

(Here, I sync three folders called ProbablySpam, ShortTermArchive and LoopProblems).

Again, nice tutorial.

Cheers,

I had the same idea as you a while back and I even did a similar flow chart to explain it all.

However, I thought up a solution that allows users to use the same account without the separate “spam_checker_passed” and “spam_checker” email accounts like you have. Also it still allows users to sort into more distinct folders rather than just inbox. It wasn’t possible before the new filter by headers feature recently added, but it should work perfectly now.

I will have to migrate my email to email only accounts soon, so I should be able to update this with my results and some example files to help others.

http://krkeegan.com/archives/89-How-to-Resurrect-Procmail-and-Spamassassin-on-Dreamhost.html