Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.




1249 posts

Uber Geek
+1 received by user: 256

Subscriber

Topic # 165966 26-Feb-2015 10:25
Send private message

We run a few mail servers. Some of them using a fairly standard Dovecot, Postfix, Spam Assassain, etc type set up.

Over the last week we have been getting quite a few calls from clients who are not receiving email from clients / friends with @xtra email addresses.

We managed to get the bounced content from one of the emails and it basically says the following: "We tried to send an email to <insert our clients email address here> but your email was graylisted.  Mail failure. "  A copy of the email with relevant bits redacted is at the end of this post.

This brings up two points and three questions:

Points:
1) Normal mail servers, when email is gray / grey listed wait nnn minutes then try again and are allowed through. some people have advised those having their mail graylisted to send it again but that wont work as the send again is a completely different email according to the headers (message IDs, dates, times, subjects etc) so gets grey-listed as a new email.

2) The greylisting from our servers is due to incorrect SPF records.  no other domain is suffering from these effects.


Questions:

1) Is anyone else seeing this?
2) Is there someone from Spark / Xtra who can tell us why emails are sent back to clients instead of resent as per normal protocols / practice.
3) The SPF records seem to come back as incorrect. Have there been changes.


Ideally it would be great if someone from Spark can check their SPf records and also change the way their mail servers handle greylistings and rather than bug the client when it is greylisted, retry sending as per common practice nad only bug the client if there is a total failure to send the email. Even a notice about a delay, not a complete failure would be preferred.

At present our only resort is to white-list the @xtra.co.nz but considering the spoofing, spam and viruses we have received from that direction over the last few months / years, it is an option that we don't want to leave in place.

Regards
Shane

--------------8<----------- START SNIP ------------------------------------------------

 

On 23/02/15 6:45 pm, "MAILER-DAEMON@yahoo.com" <MAILER-DAEMON@yahoo.com>
wrote:

 

>Sorry, we were unable to deliver your message to the following address.
>
><receiver@client.domain.co.nz>:
>Remote host said:
>451 4.7.1 <receiver@client.domain.co.nz>: Recipient address rejected:
>Greylisting in effect, please come back later [RCPT_TO]
>
>--- Below this line is a copy of the message.
>
>Received: from [66.196.81.156] by nm8.access.bullet.mail.bf1.yahoo.com
>with NNFMP; 23 Feb 2015 05:42:49 -0000
>Received: from [98.139.244.49] by tm2.access.bullet.mail.bf1.yahoo.com
>with NNFMP; 23 Feb 2015 05:42:49 -0000
>Received: from [127.0.0.1] by smtp111.sbc.mail.bf1.yahoo.com with
>NNFMP;
>23 Feb 2015 05:42:49 -0000
>X-Yahoo-Newman-Id: 378838.32315.bm@smtp111.sbc.mail.bf1.yahoo.com
>X-Yahoo-Newman-Property: ymail-3
>X-YMail-OSG: rnex<redacted>U2A--
>User-Agent: Microsoft-MacOutlook/14.4.8.150116
>Date: Mon, 23 Feb 2015 18:42:43 +1300
>Subject:
>From: Sender Name <sender@xtra.co.nz>
>To: Receiver Name<receiver@client.domain.co.nz>
>Message-ID: <D1112523.5939%h sender@xtra.co.nz>
>Thread-Topic:
>Mime-version: 1.0
>Content-type: multipart/alternative;
> boundary="B_3507561768_83233"
>
>
>

 

------------------------ END SNIP -------------------->8----------------------------




nunz

Create new topic
597 posts

Ultimate Geek
+1 received by user: 98


  Reply # 1246933 26-Feb-2015 10:53
Send private message

Can't you change the configuration at your end so temporary failures don't generate a bounce?

EDIT: Sorry, I mis-read the OP. You have having problems receiving emails from xtra.co.nz email address. Ignore the above :)

1596 posts

Uber Geek
+1 received by user: 369


  Reply # 1246974 26-Feb-2015 11:50
Send private message

Its yahoo, not xtra/telecom
Xtra email is in reality, Yahoo . There may not be anything telecom/spark can do.

It not just you either, (googling  yahoo greylisting )
http://www.iredmail.org/forum/topic8739-iredmail-support-subject-failure-notice-emails-with-yahoo.html

 
 
 
 




1249 posts

Uber Geek
+1 received by user: 256

Subscriber

  Reply # 1247708 27-Feb-2015 12:13
Send private message

Spark is xtra. it is xtra domain - spark should be working on this on behalf of their clients. Isn't there a spark person lurking around here?

Here is a list of IPs we would have to whitelist to get around this.

https://help.yahoo.com/kb/postmaster/yahoo-outbound-ip-addresses-sln23997.html?impressions=true




nunz

1596 posts

Uber Geek
+1 received by user: 369


  Reply # 1247815 27-Feb-2015 13:55
Send private message

nunz: Spark is xtra.


no it isnt (at least @xtra.co.nz  isnt)
do a mxlookup. Its yahoo. You'll get no-where with telecom or yahoo.
www.xtra.co.nz => yahoo


I think , given all the yahoo/xtra issues over the years, that Spark techies have been officially silenced from making comments . Could be wrong, just what I read somewhere




1249 posts

Uber Geek
+1 received by user: 256

Subscriber

  Reply # 1253047 7-Mar-2015 22:02
Send private message

Is there a yahoo forum here with a yahoo person lurking?
Spark promised to get back re this and of yet nothing.





nunz

8027 posts

Uber Geek
+1 received by user: 387

Trusted
Subscriber

  Reply # 1256543 11-Mar-2015 18:46
Send private message

The xtra domain has needed proper spf records forever, I don't see them fixing it anytime soon. Yes it's absurd that xtra uses yahoo which practically requires you have SPF record to send to their servers yet the xtra domain has no SPF records itself, SPF is best practice it's not mandatory unfortunately.

Why can't you whitelist xtra from your greylisting?

At the end of the day greylisting is a dirty hack.



1249 posts

Uber Geek
+1 received by user: 256

Subscriber

  Reply # 1256991 12-Mar-2015 12:02
One person supports this post
Send private message

we ended up whitelisting @xtra but the issue is that we now have no protectipn against everyone who claims to be xtra and isn't.
Spam levels are up significantly since doing the white list.
Not looking forward to the next xtra hack attack.

shane




nunz

Create new topic



Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.