Astaro User Bulletin Board
Go Back   Astaro User Bulletin Board > Astaro Gateway Products > Mail Security: SMTP, POP3, Antispam and Antivirus

Welcome to the Astaro User Bulletin Board.
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 07-10-2009, 08:28 AM
Junior Member
 
Join Date: Apr 2008
Location: Hagen / Germany
Posts: 21
Default Mail with identical sender and recipient addresses

Good Morning,

I've got a problem with mail routing or spam, perhaps someone has an idea:

A mail has to be send from an application from xy@company.com to xy@company.com (identical addresses). This mail is relayed by server A (not responsible for this domain) and server B (MX-record for this domain) doesn't accept this mail. There is no SPF-record for company.com and for various reason I can't contact the administrator of server B.

What could be the reason for blocking this mails? Is it possible that a spam rule blocks mails which have identical sender and recipient?

Thanks a lot!
Reply With Quote
  #2 (permalink)  
Old 07-10-2009, 12:45 PM
BAlfson's Avatar
Moderator
 
Join Date: Mar 2007
Location: Oklahoma City
Posts: 5,317
Default

Is thiis a question about Astaro? Do you have Astaro SMTP log entries concerning one such email?

Read about "Reverse DNS" records and checking; that will help you understand how Astaro checks arriving emails.

Cheers - Bob
__________________
ACE V7 - Astaro Preferred Partner since V3
Addicted to my iPhone!
Reply With Quote
  #3 (permalink)  
Old 07-10-2009, 07:18 PM
Billybob's Avatar
Wizard
 
Join Date: Jul 2006
Location: United States
Posts: 616
Default

The remote admin might be using BATV. Or he might simply be blocking all emails *@company.com to stop back scatter since there isn't any logical reason that he should get an email sent to him by his own domain. I do that on my backup mx for spam.
Reply With Quote
  #4 (permalink)  
Old 07-11-2009, 08:49 PM
khardeveld's Avatar
Member
 
Join Date: Dec 2008
Posts: 57
Default

If you know that the mail isn't accepted, is this because you get a bounce message? If so, this mostly states a reason for the bounce (for example: 550 Relay denied). This helps a lot in telling what is going on, so if you could provide this info....
Reply With Quote
  #5 (permalink)  
Old 07-15-2009, 02:44 PM
Junior Member
 
Join Date: Apr 2008
Location: Hagen / Germany
Posts: 21
Default

Thank you for your answers, I got more detailed information:

Server B is an Astaro 7.403 with a Sender Blacklist entry like *@company.com, so no incoming mail will be delivered if the senders address is an internal @company.com address. Additional to that there is an exception rule for this special application, that this host is excepted by all filters (e.g. spam filter).

Although I set this exception, the mail returned to sender with the following information:

<abc@company.com>: host xyz said: 550 Access denied
(sender blacklisted) (in reply to RCPT TO command)

Is it possible, that I can't ignore the senders blacklist by an exception? Does anyone have another idea to solve that problem?

thanks a lot!
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 03:37 PM.

 

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.


These pages are specifically maintained for the discussion of firewall issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases. issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases.