-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, a plea for help from a Courier newbie.
I've just installed the courier mail system (on Linux),
with the intent to download all my email into IMAP, rather
than downloading it directly into an MUA (e.g. KMail)[1].
- From what I can gather, a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Following up from my previous email, I've done a bit of investigation
to try and find out why I get a Syntax Error when getting fetchmail
to deliver mail to the courier SMTP daemon.
Looking at the mail log when mail is delivered, I get the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oops... this should have gone to the list, not just Juha...
On Monday 03 June 2002 21:13, Juha Saarinen wrote:
On Mon, 3 Jun 2002, Samuel Penn wrote:
- From what I can gather, a sensible way of doing this is to
use fetchmail to get my email
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 04 June 2002 15:08, Sam Varshavchik wrote:
Samuel Penn writes:
I can get fetchmail to rewrite the recipient, but this doesn't
appear to have any effect, except that sam@localhost becomes
sam@wotan or [EMAIL PROTECTED] (wotan being
Hi,
Does sqwebmail have to run on the same machine as the courier
mail server? I'd like to have webmail running on an OpenBSD
box, with Courier running on a different (Linux) box. I don't
want to mount network drives between the two machines.
Is this possible?
If not, does anyone have
I've had couriermlm running for the last couple of years just great,
with no problems at all. Some time in the last couple of weeks, it
has started failing to send to one person.
I get the following error:
courieresmtp: 554 SMTP service not available
This happens for standard messages out from
The reason given for mail rejection by the destination server is:
Error 554 as mentioned in the bounce is due to our servers correctly
terminating the connection with any mail server, that doesn't have what's
called reverse DNS look-up enabled. This is deemed non acceptable
according to
On Sunday 07 March 2004 09:47, Bill Taroli wrote:
Well, if it's anything like the check SA does -- and the one we've been
talking about implementing a separate filter for (using bits of SA and
Mail::CheckUser) testing mail servers -- then the DNS that owns the
address range your IP is in would
On Sunday 07 March 2004 09:57, Phillip Hutchings wrote:
On 7/03/2004, at 10:16 PM, Samuel Penn wrote:
The reason given for mail rejection by the destination server is:
Error 554 as mentioned in the bounce is due to our servers correctly
terminating the connection with any mail
On Sunday 07 March 2004 10:15, Phillip Hutchings wrote:
I was afraid of that. Another option would be to have courier mlm send
all outgoing email via smtp.ntlworld.com, which is my ISP's server. I
only actually need ESMTPD for incoming email.
Is this possible? My local DNS MX record is
I've just installed Courier on a Gentoo Linux box, and I'm having a
few issues getting things working. Until yesterday, I'd been running
Courier fine under SuSE for the last couple of years.
IMAP seems to be working, and I can login and read my old maildirs
fine (I used to have virtual users
On Saturday 26 June 2004 14:35, Samuel Penn wrote:
First, if I try to start things from the init script, things seem to
hang when starting courierfilterd:
Misreading the Gentoo init script, it's actually authdaemon that's
hanging. There's a /usr/lib/courier/authlib/authdaemond.plain, which
On Saturday 26 June 2004 20:16, Sam Varshavchik wrote:
Samuel Penn writes:
Further playing with authtest (since I think it's got to be authdaemon
related) shows that:
authtest -s esmtp -m authdaemon sam password
Gives a successful result, whilst
authtest -s esmtp -m authpam sam
On Saturday 26 June 2004 22:23, Sam Varshavchik wrote:
When authdaemon is installed it replaces all other authentication modules,
and the only one that's available is authdaemon. That's why '-m authpam'
does not work, because authpam is not installed, authdaemon is.
Okay. From the docs, I
On Sunday 27 June 2004 00:54, Sam Varshavchik wrote:
Both the IMAP server and the mail server use the same authdaemon module.
If one connects the other one should also connect. The above error message
claims that it can't find the filesystem socket.
The only way I can see this happening
On Sunday 27 June 2004 09:09, Samuel Penn wrote:
On Sunday 27 June 2004 00:54, Sam Varshavchik wrote:
Both the IMAP server and the mail server use the same authdaemon module.
If one connects the other one should also connect. The above error
message claims that it can't find the filesystem
Currently, Courier is getting my mail from some POP3 accounts via
fetchmail. These deliver to the Courier ESMTP server which accepts
them fine.
I've recently tried setting things up to accept mail directly via
SMTP for a different domain. The mail reaches my server, then is
bounced back to my
On Monday 03 January 2005 19:09, William Hue wrote:
Sam,
If the domain is listed only in esmtpacceptmailfor, then courier
acts as a relay for that domain--it accepts the e-mail, then looks
up the MX record for that domain and sends it there.
Ah, I read 'accept' to mean would place it in
On Monday 03 January 2005 20:16, Samuel Penn wrote:
If I use hosteddomains instead of locals, then I get an unknown user
error. This possibly looks like the most promising way forward however.
I'm guessing that I could setup USERDB to create users for this domain.
However, I just want anything
Don't know if my last email got through (about setting an alias to
get things to work), but though it worked for the new domain, it
totally broke the old domain.
--
Be seeing you, http://www.glendale.org.uk/
Sam.jabber: [EMAIL
20 matches
Mail list logo
