15 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: Address book ...
FromSent OnAttachments
David EhleJan 8, 2002 10:04 am 
Roland SchneiderJan 8, 2002 10:49 am 
Sam VarshavchikJan 8, 2002 3:22 pm 
DavidJan 8, 2002 3:33 pm 
Greg OwenJan 8, 2002 6:30 pm 
David EhleJan 8, 2002 8:45 pm 
Juha SaarinenJan 8, 2002 8:53 pm 
David EhleJan 8, 2002 8:57 pm 
Juha SaarinenJan 8, 2002 9:01 pm 
David EhleJan 8, 2002 9:09 pm 
Juha SaarinenJan 8, 2002 9:14 pm 
David EhleJan 8, 2002 9:19 pm 
Sam VarshavchikJan 8, 2002 9:32 pm 
Mark BrownJan 9, 2002 2:03 am 
Greg OwenJan 9, 2002 6:02 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Re: Address book and Courier-MTAActions...
From:David Ehle (eh@agni.phys.iit.edu)
Date:Jan 8, 2002 8:45:43 pm
List:net.sourceforge.lists.courier-users

Hmm Well I telneted to port 25 and tried: RCTP TO: <use@agni.phys.iit.edu use@agni.phys.iit.edu> RCTP TO: <use@agni.phys.iit.edu,use@agni.phys.iit.edu> RCTP TO: <use@agni.phys.iit.edu, use@agni.phys.iit.edu> RCTP TO: <use@agni.phys.iit.edu;use@agni.phys.iit.edu> RCTP TO: <use@agni.phys.iit.edu; use@agni.phys.iit.edu>

and All gave me a syntax error or unknown user.

I think ONLY one mailbox per RCTP TO statement is allowed ( which seems to be inaccordance with the RFC)

Also it gives the RFC821 non compliance message if anything precedes the <mbox@domain> statement.

Something like RCPT TO: <mbox@domain> "first last" WILL be accepted but I have no idea if the data is registered anywhere.

The other odd thing is that while testing I ended giving it a LOT of bad commands.. and it seems that the replys, positive OR negative got slower and slower... up to several minutes wait between command replys.

This seems odd... I don't remember for sure but Courier does spawn children to handle multiple connections at a time right? And default is what, 10? It occurs to me that if the behavior i'm seeing isn't an aberration, this could lead to DOS... a REALLY bad, or malicious client could send many bad commands and repeatedly connect - jamming up the works indefinitely due to the lengthening reply time.

Any way that aside, the proper way to send to multiple recipients would be: RCTP TO: <user1@domain> RCTP TO: <user2@domain> RCTP TO: <user3@domain> RCTP TO: <user4@domain>

Correct?

Thanks, David. Greg Owen wrote:

On Tue, 2002-01-08 at 18:52, David wrote:

I was sure it was a Squirrelmail's Problem, but I was sure that If I came here I could find out EXACTLY what they were doing wrong. So they need to parse the addresses out and send them one at a time. I thought that might be it, but how they are doing it is so grossly out of line I thought I must have been confused ;)

For what it is worth, that error looks like exactly the error I've seen with N+1 mail clients where the user expects ',' to be a valid email address seperator, when it is not. (';' is usually what the client expect in these cases).

In some email clients (one of the Outlook variants seems to ring a bell here) this is configurable. I've no idea about squirrelmail.