At 00:43 2002-04-30 -0400, Humberto Rodriguez did say:
[snip - a procmail log showing a bounced message you recieved. I fail to
see the significance of it WRT the problem you're describing]
Subject: Returned mail: see transcript for details
Folder: /var/spool/mail/arlen
Apr 29 21:50:05 dns1 sendmail[20937]: g3U1o5h20935:
to=Humberto Rodriguez [mailto:neighbors(_at_)arlenbeach(_dot_)com],
I don't know if you mailed it this way, or if this really was in your
message, but 'mailto:' isn't valid for an email address during SMTP
transit. MS Outlook apparently likes to automatically chuck that into
messages however, which will be a problem if you continue to use that MUA
while discussing email issues such as this, because what you write isn't
what you send, and what others write, isn't how OutBreak is going to show
it to you.
ctladdr=arlen (537/502), delay=00:00:00, xdelay=00:00:00,
mailer=esmtp, pri=30640, relay=arlenbeach.com], dsn=5.1.2,
stat=Host unknown (Name server: arlenbeach.com]: host not
found)
This is anm error emitted by sendmail reporting a DNS lookup
failure. Perhaps your system isn't configured for DNS properly, or the
zone for the domain in question is hosed?
ArlenBeach.com is a virtual host on my server. The email
If the host doesn't _resolve_ via DNS, it doesn't really matter where the
host is ultimatley hosted - sendmail is trying to find the MX host to send
the message to. Not a procmail issue.
print MAIL <<EndofTEXT;
[snip - perl, which isn't what the procmail list is about - if your problem
lies within your perl script, you should head to the comp.lang.perl heirarchy]
-----Original Message-----
From: Humberto Rodriguez [mailto:neighbors(_at_)arlenbeach(_dot_)com]
Thwacked yet again by your MUA. The email address should have <brackets>
around it, or the nametext should have quotes or parens. We can't begin to
diagnose your problem if the provided information is incomplete or mangled.
-----Original Message-----
From: Humberto Rodriguez [mailto:humrod(_at_)telocity(_dot_)com]
Sent: Monday, April 29, 2002 8:32 PM
To: neighbors(_at_)arlenbeach(_dot_)com
Subject: RE: test 29
I got news for you, but these are not complete headers - for instance, the
Reply-To that your script is supposedly generating isn't shown, and the
envelope sender isn't there, etc. Try emitting the message to a text file
and using a UNIX mail program to send the message instead of using
Outlook. Also, see whether a UNIX mail program (or ANY mail program other
than Outlook) processes the message for the proper reply address - if they
do, then you'll know that your problem is OutBreak.
*MICROSOFT OUTLOOK* pretty much IGNORES RFC822, the 20 year old standard
for email addressing. The newer versions seem to be ignoring incrementally
more things about RFC822.
Notably, most list messages are identified with the From: showing the
SENDER (list) address, not the actual From:, and the reply may not actually
go to the Reply-To: address.
Here is the recipe I am using:
[snippety-do]
| perl $HOME/cgi-bin/list/send.cgi
FTR, "cgi" is common gateway interface. It has to do with http interfacing
to scripts. If your script is a plain perl script, calling it a cgi is
misleading, because no doubt it doesn't retrieve it's variables or
interract with the user via HTTP. Minour point, but as long as we're
passing by...
Well, what am I doing wrong? Why is it impossible to reply
to a message and have it behave the same as the original?
I'd say it's your MUA, which made a royal mess of your post as well. If
procmail is handing the message to your perl script properly, your problem
here doesn't sit with procmail.
there an easier way to verify the email of the sender, strip
attachments and mail messages, reply messages and forward
messages to a list?
There are lots of ways to skin a cat. You have multiple steps you want to
perform - stripping attachments being the most significant of them, and so
an external script is a sensible way to approach it.
You need to diagnose whether this addressing problem you are having is with
the messages themselves or with your MUA, then go from there. As long as
you use OutBreak, you're going to experience weirdisms though - if you like
the client, you'll have to like living with it's inability to get along
with the rest of the internet outside of what Microsoft would like it to be.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail