On 30/11/2004, at 9:35 AM, Pollywog wrote:
On 11/29/2004 08:25 pm, Jay Lee wrote:
Courier IMAP does not handle delivery of the message so it should not
care
whether the message is to some...@somedomain.com or
some...@somedomain.com (or some...@somewhereelse.com for that
matter). As long as it shows up in that user's Maildir it will
display it
as a message. Might you be referring to maildrop or Courier-MTA?
What I am doing is using Postfix to receive mail on post 26, then it
passes
mail (without the spam) to port 25. Courier MTA is listening on that
port
and that is where I have a problem. I am trying to find out if I can
disable
Courier MTA without having an effect on Courier IMAP. When I have
done that,
the problem should be solved. Thanks.
Um, what? Mail comes in on port 25, listening on port 26 won't help
you. I also wouldn't recommend using a port under 1024 for any
non-standard service.
Courier itself delivers to user...@somedomain.com fine - I use it all
the time. Make sure DEFAULTDELIVERY in courierd is set to maildrop, and
that you don't have a .courier-default doing things with it.
19 messages in net.sourceforge.lists.courier-usersRe: [courier-users] extended addresses
