Just another ASSP newcomer (but long-time perl programmer) joining
in with the brainstorm, because it's a fascinatingly bizarre problem.....

In article <[EMAIL PROTECTED]>,
Micheal Espinola Jr <[EMAIL PROTECTED]> wrote:
> Fritz Borgstedt wrote:
> >> The bad attachment rejecting is only occurring with one
> >> particular recipient when sent from one particular sender.
> >>     
> 
> To clarify, it seems that the "bad attachment" rejection is only
> occurring with one (problem) recipient when sent from one particular
> sender, and only when there is more than one recipient.  If the same
> message is re-sent only to the (problem) recipient, it comes through fine.

Does it only occur with one particular message (content), or with any
message using that combination of From, To and Cc?

> There is no actual attachment in the message.  This effects the
> (problem) recipient whether they are listed in the TO, CC, or BCC, and
> there are multiple recipients.

If it happens with Bcc too, that tells us something, because a Bcc recipient
will only appear in a RCPT TO command in the SMTP exchange, and not in any
of the email headers.

It's difficult to give concrete suggestions without a copy of the email
in question (yes, I realise there are confidentiality concerns). Ideally,
run ethereal on the same server as ASSP, monitoring port 25 traffic. This
will capture everything exactly as ASSP sees it.

Cheers
Tony
-- 
Tony Mountifield
Work: [EMAIL PROTECTED] - http://www.softins.co.uk
Play: [EMAIL PROTECTED] - http://tony.mountifield.org

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to