EmailDiscussions.com - Fastmail blocked or me???

EmailDiscussions.com (http://www.emaildiscussions.com/index.php)

- FastMail Forum (http://www.emaildiscussions.com/forumdisplay.php?f=27)

- - Fastmail blocked or me??? (http://www.emaildiscussions.com/showthread.php?t=33163)

Fastmail blocked or me???

I am trying to send email from my Fastmail account (tried both Thunderbird and webmail) and all messages sent to a certain provider are coming back to me with the message "undelivered mail returned to sender". I can't figure out if it is my IP address that is blocked or Fastmail... still have to learn how to read all that techniccal mambo jambo :)

This is what is stated in the email:

This is the Postfix program at host frontend1.messagingengine.com.

I'm sorry to have to inform you that your message could not be
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to <postmaster>

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The Postfix program

<xxxxxx@chello.nl>: host smtp.chello.nl[xxxxxx.243.2] said: 551 Mail from your
IP is currently blocked based on RBL listing (in reply to RCPT TO command)

Reporting-MTA: dns; frontend1.messagingengine.com
X-Postfix-Queue-ID: CDC83C5956D
X-Postfix-Sender: rfc822; me@fastmail.fm
Arrival-Date: Thu, 17 Feb 2005 12:14:20 -0500 (EST)

Final-Recipient: rfc822; xxxxx@chello.nl
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; host smtp.chello.nl[xxx.46.243.2] said: 551 Mail
from your IP is currently blocked based on RBL listing (in reply to RCPT TO command)

Hanneke

This same thing happened to me a couple of days ago when trying to respond to an e-mail. I'm still waiting to hear back from FM support.

Quote:

<xxxxxx@chello.nl>: host smtp.chello.nl[xxxxxx.243.2] said: 551 Mail from your IP is currently blocked based on RBL listing (in reply to RCPT TO command)

unfortunately, it looks like FM is on a block list today:
http://openrbl.org/ip/66/111/4/26.htm

Last year we got daily downtime from server crashes. This year we get daily downtime from Spamcop.

Date Thu, 17 Feb 2005 12:34 PM
From MAILER-DAEMON@unspecified-domain [Add]
To <me>
Subject Undelivered Mail Returned to Sender Show full header

This is the Postfix program at host frontend1.messagingengine.com.

I'm sorry to have to inform you that your message could not be
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to <postmaster>

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The Postfix program

<them>: host
their.server[###.###.###.#] said: 591 Your host
[66.111.4.26] is blacklisted by bl.spamcop.net. Include copy of this bounce
message for help. Send your questions to blacklist-adminATsstar.com (in
reply to RCPT TO command)

SpamCop interferes again

Yes, this is SpamCop interfering again, because, in their words, there have been two reports of spam sent from fastmail in the last 17 days. Specifically, "Listing History:
In the past 16.6 days, it has been listed 2 times for a total of 26 hours".

Y'know, if someone like me "bounces" spam back, since the recipient is often someone other than the actual recipient, they'd probably see it as spam. This suggests that bouncing might not be the best way to dispose of junk mail. Maybe delete only should be the policy.

Suggestions?

Re: SpamCop interferes again

Quote:

Originally posted by disneylogic
Yes, this is SpamCop interfering again, because, in their words, there have been two reports of spam sent from fastmail in the last 17 days. Specifically, "Listing History:
In the past 16.6 days, it has been listed 2 times for a total of 26 hours".

actually more than 2 reports ... here's the latest from SpamCop.
(Some good news maybe - it looks like the latest problem has been marked as resolved ?)

Code:

-- SPAM SOURCE REPORT --

IP Address      Start/Duration Trap User Mole Simp Additional comments

    66.111.4.26  Feb 16 11h/1    0    8    0    0 delisted manually, marked resolved

    66.111.4.25  Feb 11 17h/3    0   14    0    0 marked resolved

Quote:

Originally posted by disneylogic
Y'know, if someone like me "bounces" spam back, since the recipient is often someone other than the actual recipient, they'd probably see it as spam. This suggests that bouncing might not be the best way to dispose of junk mail. Maybe delete only should be the policy.

Suggestions?

Delete only seems to be the best way to go - avoids adding grief to "joe-jobs" via returns to (forged) senders,
saves your own bandwidth, and avoids exposing your actual FM account name (if bouncing from an alias) ...
(It would be nice to be able to reject at SMTP level, but failing that, post-receipt filtering and deletion is probably
the next best thing).