Home.... | log in.... | Pub my question! | Sign-up....
Java-index >> E-Mail, Calendar, & Collaboration >> Sun Java System Messaging Server

wrong Return-path

Hi all,

I am running Messaging Server on a redhat machine:

[root@inca-mta1 log]# imsimta version

Sun Java(tm) System Messaging Server 6.2-7.05 (built Sep 5 2006)

libimta.so 6.2-7.05 (built 11:54:56, Sep 5 2006)

Linux inca-mta1 2.4.21-47.ELsmp #1 SMP Wed Jul 5 20:30:30 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux

I have a problem when messages are sent to some big lists, of which some users are not deliverable-to (quota exceeded, empty nested list, server unreachable in case of forwarded-recipients, and so on). In these cases, the bounced mail notification is sent to the original recipient of the message (the list) instead of the sender.

Note that all this occours on the frontend server, which should NEVER, afaik, write the return-path header of a message. I've noted that the header is written when the message is routed to the process channel because of the delivery error: this is an abstract from the log (i've put return-path and from in log_header.opt so these headers are logged):

=======LOG START==========

01-Jun-2007 10:07:25.36 tcp_frompmx tcp_localE 81 l.fransesini@inca.it rfc822;comprensori-inca@inca.it pfiorini@tosc.cgil.it <000e01c7a423$81170a90$6d00a8c0@domain>

01-Jun-2007 10:07:25.36 tcp_frompmx tcp_localE 81 l.fransesini@inca.it rfc822;comprensori-inca@inca.it stoti@tosc.cgil.it <000e01c7a423$81170a90$6d00a8c0@domain>

01-Jun-2007 10:07:25.36 > From: politiche-previdenziali <l.fransesini@inca.it>

01-Jun-2007 10:07:25.37 tcp_frompmx processE 81 rfc822;zone-inca@inca.it zone-inca@inca.it <0JIY00J1M6KDGS30@inca-mta1.inca.it>,<000e01c7a423$81170a90$6d00a8c0@d omain>

01-Jun-2007 10:07:25.37 > Return-path: <zone-inca@inca.it>

01-Jun-2007 10:07:25.37 > From: politiche-previdenziali <l.fransesini@inca.it>

01-Jun-2007 10:07:25.37 tcp_frompmx processE 2 rfc822;postmaster@inca.it postmaster@inca.it <0JIY00J1O6KDGS30@inca-mta1.inca.it>,<000e01c7a423$81170a90$6d00a8c0@d omain>

01-Jun-2007 10:07:25.37 > Return-path: <zone-inca@inca.it>

01-Jun-2007 10:07:25.37 > From: politiche-previdenziali <l.fransesini@inca.it>

01-Jun-2007 10:07:25.38 tcp_topmxD 81 l.fransesini@inca.it rfc822;comprensori-inca@inca.it comprensori-inca@inca.it <000e01c7a423$81170a90$6d00a8c0@domain> dns;[192.168.10.100] (localhost ESMTP PMX proxy ready) smtp;250 OK

01-Jun-2007 10:07:25.38 tcp_topmxD 81 l.fransesini@inca.it rfc822;lista-indirizzi-sede-nazionale@inca.it lista-indirizzi-sede-nazionale@inca.it <000e01c7a423$81170a90$6d00a8c0@domain> dns;[192.168.10.100] (localhost ESMTP PMX proxy ready) smtp;250 OK

01-Jun-2007 10:07:25.38 tcp_topmxD 81 l.fransesini@inca.it rfc822;lista-uffici-inca-estero@inca.it lista-uffici-inca-estero@inca.it <000e01c7a423$81170a90$6d00a8c0@domain> dns;[192.168.10.100] (localhost ESMTP PMX proxy ready) smtp;250 OK

==========LOG END==========================

I've tried to add the noaddreturnpath keyword in the default line of imta.cnf, but to no advantage.

Any help would be really appreciated.

Thanks in advance.

[3206 byte] By [claudio_tassinia] at [2007-11-27 6:07:51]
«« is there any complete sample with its execution steps for kerberos?
»» JLabel text eclipsed by background picture.
# 1

Hi,

> I have a problem when messages are sent to some big

> lists, of which some users are not deliverable-to

> (quota exceeded, empty nested list, server

> unreachable in case of forwarded-recipients, and so

> on). In these cases, the bounced mail notification

> is sent to the original recipient of the message (the

> list) instead of the sender.

For the mailing list, what have you set as the mgrperrorsto: attribute?

If you have not set this value then the behaviour you are describing is correct, what you actually have is a mailing group (not a list). This question has been raised many many times before.

Sending bounces back to the sender is not what I would consider the correct behaviour, much better to send to the list owner i.e. set mgrperrorsto: <list owners email address>

At the end of the day it is the owner/maintainer of the list that can fix the list, not the sender of the email.

Regards,

Shane.

shane_hjortha at 2007-7-12 17:09:29 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 2

> Sending bounces back to the sender is not what I

> would consider the correct behaviour, much better to

> send to the list owner i.e. set mgrperrorsto: <list

> owners email address>

>

> At the end of the day it is the owner/maintainer of

> the list that can fix the list, not the sender of the

> email.

>

That's true. But I would also like to know if a message I send to all-the-people@mydomain is not delivered to one of the users because his mailbox is full.

claudio_tassinia at 2007-7-12 17:09:29 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 3

Hi,

> That's true. But I would also like to know if a

> message I send to all-the-people@mydomain is not

> delivered to one of the users because his mailbox is

> full.

Do you mean 'you' as the general sender to the email address or 'you' in the capacity as a postmaster/administrator of the system? If the latter, then just set mgrperrorsto: to be your postmaster/admin address.

Also consider if other people are sending to the list, and if bounces were to go back to their account, this could 'spam' their account (if there are sufficient over-quota people/forwarding addresses broken etc.)

The 'return bounces back to sender' behaviour was added back into messaging server, you can use:

mgrperrorsto: /

"A value "/" given as an [envelope_from] nonpositional alias parameter, as an errors to positional alias parameter, or as a value of the mgrpErrorsTo LDAP attribute is now interpreted as a request to revert to using the original envelope from address for the incoming message while retaining mailing list semantics. This can be useful for setting up mailing lists that report all forms of list errors to the original sender. "

Please note however you need to run a recent (6.3) version of messaging server to get it working. The 6.3 upgrade patch has just been released and you can get it from the sunsolve patch website.

Regards,

Shane.

shane_hjortha at 2007-7-12 17:09:29 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
E-Mail, Calendar, & Collaboration
Sun Java System Messaging Server

E-Mail, Calendar, & Collaboration Hot Topic

E-Mail, Calendar, & Collaboration

All Classified