Page 1 of 1
Strange reaction on setSender and/or setReturnPath
Posted: Sat Mar 14, 2009 12:50 pm
by HHahn
When I use $message->setSender ("
info@domain.tld") and/or $message->setReturnPath ("
info@domain.tld"), some destination domains react by inserting a header line:
Code: Select all
Received: from nork.store ([192.168.40.9])
by bjorn-cg-01.store (RZmta 18.25) with ESMTP id x0569bl2EHAOEw
for <h.hahn@senderdomain.tld>; Sat, 14 Mar 2009 18:34:04 +0100 (MET)
Received: (from Unknown UID 1071880@localhost)
by post.webmailer.de (8.13.1/8.13.7) id n2EHY3wI018538;
Sat, 14 Mar 2009 17:34:03 GMT
X-Authentication-Warning: nork: Unknown UID 1071880 set sender to info@domain.tld using -f
What primarily ennoys me here is the last line (with the "X-Authentication-Warning:"). Does this suggest there is a spam suspicion?
The previous entry also is a bit strange ("unknown UID"
, a German domain although the message was both sent from and addressed within the Netherlands [sorry, the ISP is German...]).
Exactly the same thing happens when I use setHeader("Sender", "
info@domain.tld") instead of setSender (and/or the same for Return-Path).
(Note that I edited the e-mail addresses in the above code example. In reality I used existing addresses.)
[EDIT]
I am aware that this is unlikely to be a Swiftmailer problem. But having studied the header structures to a much larger extent than I ever did, you may be able to just give me a hint...
Re: Strange reaction on setSender and/or setReturnPath
Posted: Sat Mar 14, 2009 5:51 pm
by Chris Corbyn
That's weird and I'm not sure I can offer a very correct answer. It looks like a misconfiguration with the mail server, which seems to be complaining about the level of authority in order to pass along the Sender header from it's own domain. That's what I deduce from the header it's adding, but I could be wrong.
It's saying that in order to pass those headers, it (the MTA... the SMTP software itself) must be invoked with the "-f" flag (sounds like a Sendmail-like MTA). That's nothing to do with Swift Mailer though and is a server-admin issue.
Re: Strange reaction on setSender and/or setReturnPath
Posted: Sat Mar 14, 2009 5:52 pm
by Chris Corbyn
What Transport are using using?
Re: Strange reaction on setSender and/or setReturnPath
Posted: Sun Mar 15, 2009 8:27 am
by HHahn
Chris Corbyn wrote:What Transport are using using?
Currently I am using Swift_MailTransport. However, I intended to use SMTP, but this ISP (Strato, by the way) requires authenticated SMTP, and my customer currently cannot find his POP3 login name and password... (the ISP requires the same login data for ASMTP as for POP3).
Swift_SendmailTransport isn't an alternative either in this case, as this ISP seems to implement this via SMTP, and the SwiftMailer Sendmail transport doesn't seem to allow passing login data. (Might this be a hint for a further improvement of SwiftMailer: optional login data passed into Sendmail transport?)
Re: Strange reaction on setSender and/or setReturnPath
Posted: Sun Mar 15, 2009 8:39 am
by HHahn
As I am still in a test phase with Swift Mailer, I am sending the test mails to two different addresses belonging to me (one of them redirects to the other).
I first noticed the Aithentication warning in the redirected messages. But later I saw them in the othe rmessages as well, but at another position in the header. It is always preceded by this
Code: Select all
# Received: (from Unknown UID 1071880@localhost)
# by post.webmailer.de (8.13.1/8.13.7) id n2EHY3wI018538;
# Sat, 14 Mar 2009 17:34:03 GMT
section, suggesting (by the ".de" TLD) that it is indeed the sender's ISP who inserts it. It even remains doing so when I replace the "noreply" address by a really existing one.
[EDIT:]
This Authentication warning is also inserted if I do not use "Sender:" or "Return-Path:". I'll contact the ISP about it.
In a few days I'll also start experimenting with SwiftMailer for another customer, with another ISP.
Re: Strange reaction on setSender and/or setReturnPath
Posted: Sun Mar 15, 2009 7:44 pm
by Chris Corbyn
The "Unknown UID" portion is concerning but has nothing to do with Swift Mailer.
I did some googling and it seems that this appears when PAM is not correctly configured (pam is an authentication method used at the Linux system level). Basically sendmail/postfix/exim or whatever the MTA is is trying to check the user information (the Linux user that is) via pam, and failing.
Your host really need to respond to this and let you know why that is. It's either a bug on their server, or a deliberate attempt to restrict access to sendmail.
Re: Strange reaction on setSender and/or setReturnPath
Posted: Mon Mar 16, 2009 3:44 am
by HHahn
Chris Corbyn wrote:The "Unknown UID" portion is concerning but has nothing to do with Swift Mailer.
I did some googling and it seems that this appears when PAM is not correctly configured (pam is an authentication method used at the Linux system level). Basically sendmail/postfix/exim or whatever the MTA is is trying to check the user information (the Linux user that is) via pam, and failing.
Your host really need to respond to this and let you know why that is. It's either a bug on their server, or a deliberate attempt to restrict access to sendmail.
Thanks. Do I understand you correctly that this problem is likely to be over when I use SMTP?
Re: Strange reaction on setSender and/or setReturnPath
Posted: Mon Mar 16, 2009 4:24 am
by Chris Corbyn
HHahn wrote:Thanks. Do I understand you correctly that this problem is likely to be over when I use SMTP?
Yes. This problem cannot exist when using SMTP.