Topic: 530 5.7.1 relay restricted -Qmail

[Anonymous]

I am running SME 5.6 as a server and gateway. The box is being used for e-mail only.

I have ASSP installed.

Once in a while someone will send us mail and it will be rejected with the following notice (the following comes from a mail I sent to myself while dialed into a remote computer using that computer's e-mail account):


Subject: Non delivery report: 5.7.1 (Delivery not authorized)

Your message

 From:   John Doe <johnd@acompany.com>

 To:   del@bcompany.com

 Subj:   042204-orig.ace
 Sent:   2004-04-22 16:49

has encountered a delivery problem.

Reason: Delivery not authorized
The sender is not authorized to send to the destination.
This can be the result of per-host or per-recipient filtering.

Transcript of session:
RCPT TO:<del@bcompany.com>
530 5.7.1 relay restricted

**********************

Without making any changes on our system mail from the denied sender may then come through. (Though it could be blocked again and I would never know if no one complained.)

I thought ASSP might be bouncing the mail back.  The log, though, shows the above mail made it through marked OK.

The mail log for the failed attempt is:

@400000004088353703cc9e3c new msg 1441890
@400000004088353703ccb994 info msg 1441890: bytes 5136741 from <johnd@acompany.com> qp 25451 uid 401
@4000000040883537044dc4bc starting delivery 10716: msg 1441890 to local alias-localdelivery-del@bcompany.com
@4000000040883537044de7e4 status: local 1/10 remote 0/20
@40000000408835372289b29c new msg 1441877
@40000000408835372289d1dc info msg 1441877: bytes 5136863 from <johnd@acompany.com> qp 25475 uid 400
@400000004088353722f1e664 starting delivery 10717: msg 1441877 to local del@monk.bcompany.com
@400000004088353722f345f4 status: local 2/10 remote 0/20
@400000004088353722f93d4c delivery 10716: success: forward:_qp_25475/did_0+0+1/
@400000004088353722fcc3a4 status: local 1/10 remote 0/20
@400000004088353722ff34a4 end msg 1441890


*****
The log entry for the second (successful) attempt:

@400000004088357f1d718f3c new msg 1441891
@400000004088357f1d71ae7c info msg 1441891: bytes 5134158 from <johnd@acompany.com> qp 25462 uid 401
@400000004088357f1df0a664 starting delivery 10723: msg 1441891 to local alias-localdelivery-del@bcompany.com
@400000004088357f1df0c5a4 status: local 1/10 remote 1/20
@40000000408835800322835c new msg 1441877
@40000000408835800322a29c info msg 1441877: bytes 5134280 from <johnd@acompany.com> qp 25508 uid 400
@4000000040883580054db82c starting delivery 10724: msg 1441877 to local del@monk.bcompany.com
@4000000040883580054dd76c status: local 2/10 remote 1/20
@4000000040883580054ddf3c delivery 10723: success: forward:_qp_25508/did_0+0+1/
@4000000040883580054deedc status: local 1/10 remote 1/20
@4000000040883580054df6ac end msg 1441891


The problem, as I said, seems to happen rarely.  If a person sends a mail that is denied other mail from the same sender may get through.

I've searched the forums but didn't find anything for 'relay restricted.'

Monk is the name of our mail server.  There is an entry for monk.combanyb.com in ASSP and SME has created the appropriate Hostname with a Location of Self.

Any help will be appreciated.

[DWells]

Should this be of help to anyone else ...

In the week that has passed since I posted the above question the problem has not recurred.  We've received mail on a regular basis from people who had problems before.

I do not know that anyone who received the 5.7.1 notice ever received another after we had mailed them something, which would lead me to believe that having them added to the ASSP whitelist solved the problem (even though it looked like the mail made it past ASSP).

After some additional problem solving it dawned on me that our sister company had trouble e-mailing us in August, just after I put SME server in use; I don't recall if the problem occurred before or after ASSP was added -- and the problem was so short lived I didn't worry too much about it (this was about the time of SOBIG, so I had other things going on.) Anyway, they were getting the 5.7.1 error.

The thing that is certainly in common is that after fresh installs of SME Server (probably with ASSP in place) in August and April some people (very few) had trouble getting mail through sometimes -- they received 5.7.1 errors. With no tweaking on my end the problem vanished. [After the August episode the problem never recurred until the April e-mail server replacement.]