[quote]All MUAs that I’ve seen allow you to set these headers correctly.
All? Eudora? Not the copy that I have. OE? I don’t think so, although I could be wrong.
expect people to send from firstname.lastname@example.org - the MX for domain.com is set to
mail.domain.com (or server.dreamhost.com sometimes) and you retrieve mail
from ‘mail.domain.com’ because this is a different machine from your user
machine. There’s no reason that we should necessarily accept mail for
There is if there are going to be outgoing headers generated by at least one well-established email client that contain “mail.domain.com” due to the settings you recommend.
[quote]Also my test before would seem to imply that the bounce would go to the
sender (ie the ‘From’ address) and not to the address in the return path.
I will do some more research on this but I believe that the return path is
only used if the From address is invalid.
Perhaps a bounce generated by Dream Host’s servers would go to the “From” address, but I do believe that many servers prefer a Return-Path – or even Errors-To address, if either is present. remember, we’re talking about bounces being generated not only by Dream Host.
[quote]To be honest, we have over 10,000 customers and you’re the only one who
seems to have a problem with this (that I have heard from in two years of
working here anyway).
Yes, but we both know that doesn’t mean there’s not a problem.
To come across this:
- a user would have to anticipate getting a bounce message, and realize that it hadn’t been delivered.
- the user’s mail client or MTA would have to generate headers the same way my client and ISP do.
- the user would have to be using the form mail.example.com (precluding those who use machinename.dreamhost.com in conjunction with a .forward file
- the bounce would have to be generated by a server that prefers to bounce to the Return-Path or Errors-To rather than the From or Reply-To
So, because of all that – especially having to expect an incoming bounce – I wouldn’t be surprised if no one caught it before.
[quote]I agree with you in principle that
email@example.com should work as an extra precaution, but it’s
really not necessary;
[quote]generally you should send mail from
firstname.lastname@example.org and your MUA should set the Return-Path header. Again
you should probably include actual full headers rather than just
explaining what you’re doing (and include the actual settings you’re using).
[quote]The way I see it, if Dream Host tells me to pick up mail at a server
called mail.example.com, then mail sent to mail.example.com should be
We tell you to pick up mail at mail.example.com, not to
send or receive mail from mail.example.com.
Yes, I know; that’s part of what I’ve been saying… that would be part of the problem for those whose MUAs and/or MTAs generate headers like mine do.
I don’t think our setup is that unusual, and it seems to function properly
for everyone else pretty well.
I’m going to do some tests of my own to try to find out which headers are generated by Claris Emailer and which are generated by speakeasy.net.
[quote]The reason I like mutt is because it’s the best mail client available not
because it has a lot of control over email headers :> As its inventor
says… all mail clients suck - this one just sucks less.
Heh… Haven’t tried Claris Emailer, have you? It sucks least of all. That’s why so many people still use it, even though it’s now unsupported.
And as for changing clients… Like I say, Emailer has never been a problem before… and a switch to another client would involve:
a) recreation of 27+ email accounts in the new client
b) recreation of 59 filters
c) recreation of half a dozen AppleScripts (if possible in the new client)
d) archiving and/or transfer of my 75MB mail database, while
e) recreating 80 folders within the client
e) moving to an email client that probably sucks more than Emailer.
…so it would be pretty non-trivial.
No because you’re not sending mail through your user machine; you’re
sending mail through your mail machine.
I already unerstand that.
[quote]You can set it to
email@example.com and it will work fine as long as
username is a valid machine username.
And I understand that, too.
[quote]So in your case setting account to
firstname.lastname@example.org will set the Return-Path to a valid
header - the same as the way things worked with your old provider. It’s
only if you care about vanity that setting the headers to other things is
necessary; and most email clients WILL set the headers the way you’re
expecting yours to.
I’ll reserve comment on the “most email clients” thing until I do some more research. And I also have my doubts that most will allow separately-set headers.
Ok then set login to email@example.com and everything
will work as you describe - there’s no difference.
Except for the custom domain going away, natch.
For all intents and purposes, I am the tech guys.
You said you were going to talk to the programmers… That’s what I meant.
[quote]I am still considering this issue; since few people seem to have problems
with it, and since it could conceivably result in yet more UCE (spam) I’m
not sure if it’s necessary. In your case, if you write in to support they
could make your mail machine accept mail for mail.domain.com in your
particular case if it’s a big deal.
Well, I’m trying to turn it into a small deal by seeing if there’s something that can be done.
[quote]We may change this behaviour on a larger scale but it’s something I’ll
have to think about and discuss with some other folks. It would require
some programming, would increase the size of our alias files and would not
necessarily be of much benefit, while possibly having some drawbacks.
I’ll let you know what I find out about the headers I’m generating, and send you some annotated copies. Where would you like me to send them?