On 12. Mrz 2004, at 1:39, Julian Mehnle wrote:

Phillip Hutchings [EMAIL PROTECTED] wrote:
[...]
You might want to always consider the "From:" header the sender
address *for simplicity of code*, but be aware that it's just plain
wrong.

Tell that to all the people that write clients. Outlook 2000 MAY
support it, but many don't. Most webmail systems and Apple Mail (what I
use) doesn't. It may be plain wrong, but it happens a lot.


Likewise, MIME should be formatted a certain way, but 99% of
programmers seem to be unaware of this, judging by the number of
automated messages that get wrapped by courier.

Of course you are right in that a lot of software is sloppy. But that
doesn't justify advising implementors or admins to be sloppy, too. If
Lorenzo Perone is going to write his own filter, he'd better do it right.
Especially since it really isn't much of an effort to use the "Sender:"
header instead of "From:", if it's there.

As told in my last post - I recognize I just can't, and won't do that
(base the filter on the From: header - even after making sure the envelope
is not of a hosted domain).
And I never told/meant implementors are sloppy or whatever.
I would stop receiving mails I sent here, from this very list,
if I did what I meant to do at the beginning.
So, sorry for possibly misleading others.
And thanks a lot to everyone who contributed to this thread,
which has developed into an interesting and extensive exchange of
information and debate.


However - the problem exists, and it _is_ a nuisance, no matter if MUA's or
SMTP are the culprits. Still most people, "normal" users will be
misleaded.


Yes, the Sender: would be at least a hint, if courier just
added this header... there must be a way to do it it in a
maildrop filter.. (or I didn't find the right conf var/file yet)...

Second, IMO it *does* make sense to rely on the envelope sender if you
somehow verify its validity [...] and then overwrite any existing
"Sender:" header with it [...]

That's a good point. I know my domain has SPF, though I don't actually run any spf checks yet. I'm considering installing Courier::Filter's SPF filter. If a filter that processed the envelope sender and rewrote the Sender: header existed, I would probably use it. It's useful to know.

Courier::Filter, and courierfilters in general, cannot modify messages due
to a limitation in Courier, so I'm going to write a maildrop script or
something similar to do just that. I'm performing SPF checks already,
thus I consider the envelope senders of my incoming mail to be validated.
So I can just use an independent maildrop script to rewrite the "Sender:"
header. I'll post here as soon as I have a working solution.

Does anyone know under which variable, or place, the envelope address is
available in maildrop filters?
It is not automatically inserted in the mail headers - at least not in my
courier installation/conf...



Regards,


Lorenzo



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to