(no subject)
Apr. 24th, 2004 05:47 pmI've sent out another volley of DHP reminder notices. I'm using sendmail for it, which should be straightforward, I hope.
Not sure how to collect any bounce notifications that happen, though.
Anybody know if there's a way to say in the mail headers where the errors should get sent to?
Thanks to
plambert for the suggestion of method to use.
Not sure how to collect any bounce notifications that happen, though.
Anybody know if there's a way to say in the mail headers where the errors should get sent to?
Thanks to
no subject
Date: 2004-04-24 07:57 pm (UTC)2) What is your userid on that machine? (we will call it bar)
Bounces should go to bar@foo; the problem comes in if you ran your script as a user other than yourself, or if the foo machine isn't set up properly and it ends up sending things like "angelbob@localhost".
More information about the exact method you used to send things would be helpful; feel free to email me.
no subject
Date: 2004-04-24 08:00 pm (UTC)no subject
Date: 2004-04-24 09:05 pm (UTC)no subject
Date: 2004-04-24 09:27 pm (UTC)A) It doesn't know a valid name for itself, and isn't sending somebody elses name instead.
- Like "angelbob@myhouse.local", "angelbob@localhost", or "angelbob@"
or
B) It's sending something valid, like angelbob@linuxbox.angelbob.com, but
B1) There are no DNS pointers for linuxbox.angelbob.com, or
B2) linuxbox.angelbob.com isn't running a daemon listening on port 25.
Or is it some other problem entirely?
If it's A, any mail already sent isn't going to bounce properly, but users might be able to reply to it if you gave it a valid "From:" line.
If it's B1, it's just a DNS change. If it's B2, you have to set up Sendmail or some equivilent to be able to receive. In either of those cases, you can fix it now and most of the bounces will get to you, even if they bounced already. This is because DNS issues or connection-refused type problems tend to result in a wait and retry behavior, and most mail servers won't give up for several days.
no subject
Date: 2004-04-25 12:06 am (UTC)no subject
Date: 2004-04-25 01:54 am (UTC)Wanting another back rub!
no subject
Date: 2004-04-25 03:26 am (UTC)Do you have my contact info yet? I'd like to be on that list.
no subject
Date: 2004-04-25 12:13 pm (UTC)I should probably change the "From:" line to something valid but unrelated to my machine (like my Yahoo or Google address), though I think that'd increase the hazard of the mail appearing to be spam.
The "just a DNS change" isn't an easy option since I'm going through SpeakEasy, and I don't currently run my own DNS for any domain.
no subject
Date: 2004-04-25 12:14 pm (UTC)no subject
Date: 2004-04-25 12:34 pm (UTC)D'oh. Sounds like I'm gonna need to try this again.
Wanting another back rub!
Are you free Monday (like, tomorrow) evening?
sure
Date: 2004-04-25 03:57 pm (UTC)So yes, I'm free. Also, keep in mind 9:15 am Teusday is PP YET again, are you still going to be in my support network?, and if yes, are you going to want to crash here or with B rather than having to shlep home and then drive back here the next morning?
Re: sure
Date: 2004-04-25 04:05 pm (UTC)no subject
Date: 2004-04-25 04:06 pm (UTC)Re: sure
Date: 2004-04-25 04:15 pm (UTC)Re: sure
Date: 2004-04-25 04:17 pm (UTC)no subject
Date: 2004-04-25 05:24 pm (UTC)There's an "Errors-To:" header that some software uses, and some software respects, but it's not part of any internet standard, and the more recent RFCs actually discourage its use.
Not all software has the capability to see the envelope sender; consider an MTA that strips it off before giving it to another MTA; or a bounce generated by an MUA for some reason (no, it's not a spam filter. My address really is invalid, I swear!). In that case they nearly always use the From: address, but some will use Reply-To: or Errors-To: if present.
The best strategy is always this: Ensure that envelope From and header From: are the same, that they point to an address that can actually receive mail, and that both Errors-To: and Reply-To: are missing.
no subject
Date: 2004-04-25 05:51 pm (UTC)no subject
Date: 2004-04-26 09:44 am (UTC)