Menu
▾
▴
fetchmail-users — User questions and discussion
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(16) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(2) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
(8) |
Aug
(21) |
Sep
(17) |
Oct
(35) |
Nov
(39) |
Dec
(55) |
| 2006 |
Jan
(70) |
Feb
(11) |
Mar
(55) |
Apr
(27) |
May
(73) |
Jun
(47) |
Jul
(63) |
Aug
(27) |
Sep
(52) |
Oct
(39) |
Nov
(87) |
Dec
(15) |
| 2007 |
Jan
(23) |
Feb
(46) |
Mar
(108) |
Apr
(63) |
May
(54) |
Jun
(34) |
Jul
(29) |
Aug
(103) |
Sep
(46) |
Oct
(69) |
Nov
(29) |
Dec
(17) |
| 2008 |
Jan
(45) |
Feb
(32) |
Mar
(25) |
Apr
(17) |
May
(39) |
Jun
(20) |
Jul
(64) |
Aug
(31) |
Sep
(38) |
Oct
(20) |
Nov
(42) |
Dec
(50) |
| 2009 |
Jan
(10) |
Feb
(38) |
Mar
(3) |
Apr
(29) |
May
(41) |
Jun
(31) |
Jul
(21) |
Aug
(53) |
Sep
(49) |
Oct
(26) |
Nov
(28) |
Dec
(15) |
| 2010 |
Jan
(83) |
Feb
(38) |
Mar
(33) |
Apr
(44) |
May
(9) |
Jun
(16) |
Jul
(35) |
Aug
(38) |
Sep
(11) |
Oct
(35) |
Nov
(68) |
Dec
(19) |
| 2011 |
Jan
(16) |
Feb
(69) |
Mar
(42) |
Apr
(54) |
May
(56) |
Jun
(29) |
Jul
|
Aug
(65) |
Sep
(3) |
Oct
(39) |
Nov
(33) |
Dec
(4) |
| 2012 |
Jan
(31) |
Feb
(21) |
Mar
(26) |
Apr
(13) |
May
(38) |
Jun
(39) |
Jul
(14) |
Aug
(31) |
Sep
(8) |
Oct
(32) |
Nov
(12) |
Dec
(16) |
| 2013 |
Jan
(40) |
Feb
(22) |
Mar
(21) |
Apr
(15) |
May
(13) |
Jun
(9) |
Jul
(34) |
Aug
(10) |
Sep
(10) |
Oct
|
Nov
(7) |
Dec
(1) |
| 2014 |
Jan
(25) |
Feb
(9) |
Mar
(8) |
Apr
(12) |
May
(7) |
Jun
|
Jul
(7) |
Aug
(4) |
Sep
(27) |
Oct
(25) |
Nov
(18) |
Dec
(3) |
| 2015 |
Jan
(18) |
Feb
(13) |
Mar
(4) |
Apr
(19) |
May
(11) |
Jun
|
Jul
(1) |
Aug
(7) |
Sep
(6) |
Oct
(4) |
Nov
(19) |
Dec
(6) |
| 2016 |
Jan
|
Feb
(8) |
Mar
(14) |
Apr
|
May
(11) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
(10) |
Oct
|
Nov
(11) |
Dec
(17) |
| 2017 |
Jan
(17) |
Feb
(35) |
Mar
|
Apr
(4) |
May
(8) |
Jun
(2) |
Jul
(16) |
Aug
|
Sep
(5) |
Oct
(11) |
Nov
(15) |
Dec
(10) |
| 2018 |
Jan
|
Feb
(3) |
Mar
|
Apr
(3) |
May
(2) |
Jun
(8) |
Jul
|
Aug
(10) |
Sep
(17) |
Oct
(15) |
Nov
(12) |
Dec
(10) |
| 2019 |
Jan
(4) |
Feb
(14) |
Mar
(33) |
Apr
(17) |
May
(7) |
Jun
(6) |
Jul
(2) |
Aug
(4) |
Sep
(22) |
Oct
(13) |
Nov
|
Dec
|
| 2020 |
Jan
(36) |
Feb
(19) |
Mar
(31) |
Apr
(2) |
May
(22) |
Jun
(7) |
Jul
(25) |
Aug
(9) |
Sep
(17) |
Oct
(52) |
Nov
(13) |
Dec
(9) |
| 2021 |
Jan
(23) |
Feb
(13) |
Mar
(9) |
Apr
(15) |
May
(3) |
Jun
(7) |
Jul
(4) |
Aug
(23) |
Sep
(3) |
Oct
(8) |
Nov
(28) |
Dec
(9) |
| 2022 |
Jan
(38) |
Feb
(2) |
Mar
(56) |
Apr
(24) |
May
(29) |
Jun
(22) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(13) |
Nov
(2) |
Dec
|
| 2023 |
Jan
(6) |
Feb
(1) |
Mar
(1) |
Apr
(4) |
May
|
Jun
|
Jul
(21) |
Aug
(5) |
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2024 |
Jan
(15) |
Feb
(4) |
Mar
|
Apr
(4) |
May
(11) |
Jun
(9) |
Jul
(1) |
Aug
|
Sep
(9) |
Oct
(9) |
Nov
(1) |
Dec
(1) |
| 2025 |
Jan
(7) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
(10) |
Jul
|
Aug
(1) |
Sep
(12) |
Oct
|
Nov
|
Dec
|
|
From: longbow <lo...@gm...> - 2006-10-12 18:01:23
|
Rob MacGregor wrote:
> On 10/12/06, longbow <lo...@gm...> wrote:
>> hi all!
>>
>> i think i have a problem with my fetchmail (config). i use it to get all
>> the email from my various accounts. in the .fetchmailrc in my home dir i
>> put something like this:
>>
>> poll MAILSERVER protocol IMAP user "MAILBOXUSERNAME" password
>> "THESECRET" is LOCALUSER keep
>
> Can we see the file (munge username and password)? "Something like"
> isn't good enough.
here it is:
poll MAILSERVER1 protocol IMAP user "MAILBOXUSER1" password "PWD1"
is LOCALUSER keep
poll MAILSERVER2 protocol POP3 user "MAILBOXUSER2" password "PWD2" ssl
is LOCALUSER
>
> The output of "fetchmail --nosyslog -v -v" is also necessary and
> "fetchmail --configdump" would help (remember to munge username and
> password).
>
fetchmail --nosyslog -v -v
fetchmail: 6.3.4 querying MAILSERVER1 (protocol IMAP) at Thu Oct 12
17:42:05 2006: poll started
fetchmail: IMAP< * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION]
Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc. See
COPYING for distribution information.
fetchmail: IMAP> A0001 CAPABILITY
fetchmail: IMAP< * CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION
fetchmail: IMAP< A0001 OK CAPABILITY completed
fetchmail: Protocol identified as IMAP4 rev 1
fetchmail: IMAP> A0002 LOGIN "MAILBOXUSER1" *
fetchmail: IMAP< A0002 OK LOGIN Ok.
fetchmail: selecting or re-polling default folder
fetchmail: IMAP> A0003 SELECT "INBOX"
fetchmail: IMAP< * FLAGS (\Draft \Answered \Flagged \Deleted \Seen \Recent)
fetchmail: IMAP< * OK [PERMANENTFLAGS (\* \Draft \Answered \Flagged
\Deleted \Seen)] Limited
fetchmail: IMAP< * 0 EXISTS
fetchmail: IMAP< * 0 RECENT
fetchmail: IMAP< * OK [UIDVALIDITY 1159609714] Ok
fetchmail: IMAP< * OK [MYRIGHTS "acdilrsw"] ACL
fetchmail: IMAP< A0003 OK [READ-WRITE] Ok
fetchmail: 0 messages waiting after first poll
fetchmail: No mail for MAILBOXUSER1 at MAILSERVER1
fetchmail: IMAP> A0004 LOGOUT
fetchmail: IMAP< * BYE Courier-IMAP server shutting down
fetchmail: IMAP< A0004 OK LOGOUT completed
fetchmail: 6.3.4 querying MAILSERVER1 (protocol IMAP) at Thu Oct 12
17:42:06 2006: poll completed
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.4 querying MAILSERVER2 (protocol POP3) at Thu Oct 12
17:42:06 2006: poll started
fetchmail: Issuer Organization: THE ORGANIZATION
fetchmail: Issuer CommonName: Certification Authority (CA) 2005
fetchmail: Server CommonName: MAILSERVER2
fetchmail: MAILSERVER1 key fingerprint:
72:72:A9:AE:DD:11:DA:01:C4:9D:29:D8:88:C7:74:39
fetchmail: Server certificate verification error: unable to get local
issuer certificate
fetchmail: Server certificate verification error: certificate not trusted
fetchmail: Server certificate verification error: unable to verify the
first certificate
fetchmail: POP3< +OK CommuniGate Pro POP3 Server 5.0.2 ready
<88610.1160667726@MAILSERVER2>
fetchmail: POP3> CAPA
fetchmail: POP3< +OK capability list follows
fetchmail: POP3< SASL LOGIN PLAIN
fetchmail: POP3< LAST
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< PIPELINING
fetchmail: POP3< UIDL
fetchmail: POP3< IMPLEMENTATION CommuniGatePro
fetchmail: POP3< .
fetchmail: POP3> USER MAILBOXUSER2
fetchmail: POP3< +OK please send the PASS
fetchmail: POP3> PASS *
fetchmail: POP3< +OK 0 messages (0 bytes)
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for MAILBOXUSER2 at MAILSERVER2
fetchmail: POP3> QUIT
fetchmail: POP3< +OK CommuniGate Pro POP3 Server connection closed
fetchmail: 6.3.4 querying MAILSERVER2 (protocol POP3) at Thu Oct 12
17:42:08 2006: poll completed
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: Deleting fetchids file.
fetchmail: normal termination, status 1
fetchmail: Deleting fetchids file.
fetchmail --configdump
TRUE=1; FALSE=0
os_type = 'linux'
feature_options = ('pop3','imap','rpa','sdps','etrn','odmr','ssl',)
# Start of configuration initializer
fetchmailrc = {
'poll_interval':0,
"logfile":None,
"idfile":"/home/LOCALUSER/.fetchids",
"postmaster":"LOCALUSER",
'bouncemail':TRUE,
'spambounce':FALSE,
"properties":None,
'invisible':FALSE,
'showdots':TRUE,
'syslog':FALSE,
# List of server entries begins here
'servers': [
# Entry for site `MAILSERVER1' begins:
{
"pollname":"MAILSERVER1",
'active':TRUE,
"via":None,
"protocol":"IMAP",
"service":None,
'timeout':300,
'interval':0,
"envelope":"Received",
'envskip':0,
"qvirtual":None,
"auth":"any",
'dns':TRUE,
'uidl':FALSE,
"aka":[],
"localdomains":[],
"interface":None,
"monitor":None,
"plugin":None,
"plugout":None,
"principal":None,
'tracepolls':FALSE,
'users': [
{
"remote":"MAILBOXUSER1",
"password":"PWD1",
'localnames':["LOCALUSER"],
'fetchall':FALSE,
'keep':TRUE,
'flush':FALSE,
'limitflush':FALSE,
'rewrite':TRUE,
'stripcr':FALSE,
'forcecr':FALSE,
'pass8bits':FALSE,
'dropstatus':FALSE,
'dropdelivered':FALSE,
'mimedecode':FALSE,
'idle':FALSE,
"mda":None,
"bsmtp":None,
'lmtp':FALSE,
"preconnect":None,
"postconnect":None,
'limit':0,
'warnings':3600,
'fetchlimit':0,
'fetchsizelimit':100,
'fastuidl':4,
'batchlimit':0,
'ssl':FALSE,
"sslkey":None,
"sslcert":None,
"sslproto":None,
'sslcertck':FALSE,
"sslcertpath":None,
"sslfingerprint":None,
'expunge':0,
"properties":None,
"smtphunt":["localhost"],
"fetchdomains":[],
"smtpaddress":None,
"smtpname":None,
'antispam':'',
"mailboxes":[],
}
, ]
}
,
# Entry for site `MAILSERVER2' begins:
{
"pollname":"MAILSERVER2",
'active':TRUE,
"via":None,
"protocol":"POP3",
"service":None,
'timeout':300,
'interval':0,
"envelope":"Received",
'envskip':0,
"qvirtual":None,
"auth":"any",
'dns':TRUE,
'uidl':FALSE,
"aka":[],
"localdomains":[],
"interface":None,
"monitor":None,
"plugin":None,
"plugout":None,
"principal":None,
'tracepolls':FALSE,
'users': [
{
"remote":"MAILBOXUSER2",
"password":"PWD2",
'localnames':["LOCALUSER"],
'fetchall':FALSE,
'keep':FALSE,
'flush':FALSE,
'limitflush':FALSE,
'rewrite':TRUE,
'stripcr':FALSE,
'forcecr':FALSE,
'pass8bits':FALSE,
'dropstatus':FALSE,
'dropdelivered':FALSE,
'mimedecode':FALSE,
'idle':FALSE,
"mda":None,
"bsmtp":None,
'lmtp':FALSE,
"preconnect":None,
"postconnect":None,
'limit':0,
'warnings':3600,
'fetchlimit':0,
'fetchsizelimit':100,
'fastuidl':4,
'batchlimit':0,
'ssl':TRUE,
"sslkey":None,
"sslcert":None,
"sslproto":None,
'sslcertck':FALSE,
"sslcertpath":None,
"sslfingerprint":None,
'expunge':0,
"properties":None,
"smtphunt":["localhost"],
"fetchdomains":[],
"smtpaddress":None,
"smtpname":None,
'antispam':'',
"mailboxes":[],
}
, ]
}
]
}
# End of initializer
>> this runs perfect expect that the fetchmail daemon is deleting the
>> messages in the remote server's inbox. i read in the manual that
>> deleteing is the default action and adding "keep" should keep the
>> messages on the remote side. i tried it and fetchmail recognizes that
>> the config has changed by diplaying this:
>
> This isn't normal for the config you're talking about - I poll an IMAP
> server with keep and it doesn't delete the messages.
>
> The possibilities are that either you've not got a valid configuration
> or the remote server is doing something it shouldn't. The information
> I've asked for will help identify which.
well i thought so too...
>
> (Oh, and I'd suggest you read the FAQ, which details what you should
> provide when reporting something you think is a bug).
>
hope you can help me with this.
thx
longbow
|
|
From: Rob M. <rob...@gm...> - 2006-10-12 17:19:02
|
On 10/12/06, longbow <lo...@gm...> wrote:
> hi all!
>
> i think i have a problem with my fetchmail (config). i use it to get all
> the email from my various accounts. in the .fetchmailrc in my home dir i
> put something like this:
>
> poll MAILSERVER protocol IMAP user "MAILBOXUSERNAME" password
> "THESECRET" is LOCALUSER keep
Can we see the file (munge username and password)? "Something like"
isn't good enough.
The output of "fetchmail --nosyslog -v -v" is also necessary and
"fetchmail --configdump" would help (remember to munge username and
password).
> this runs perfect expect that the fetchmail daemon is deleting the
> messages in the remote server's inbox. i read in the manual that
> deleteing is the default action and adding "keep" should keep the
> messages on the remote side. i tried it and fetchmail recognizes that
> the config has changed by diplaying this:
This isn't normal for the config you're talking about - I poll an IMAP
server with keep and it doesn't delete the messages.
The possibilities are that either you've not got a valid configuration
or the remote server is doing something it shouldn't. The information
I've asked for will help identify which.
(Oh, and I'd suggest you read the FAQ, which details what you should
provide when reporting something you think is a bug).
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche
|
|
From: longbow <lo...@gm...> - 2006-10-12 09:19:34
|
hi all! i think i have a problem with my fetchmail (config). i use it to get all the email from my various accounts. in the .fetchmailrc in my home dir i put something like this: poll MAILSERVER protocol IMAP user "MAILBOXUSERNAME" password "THESECRET" is LOCALUSER keep this runs perfect expect that the fetchmail daemon is deleting the messages in the remote server's inbox. i read in the manual that deleteing is the default action and adding "keep" should keep the messages on the remote side. i tried it and fetchmail recognizes that the config has changed by diplaying this: fetchmail: restarting fetchmail (/home/USER/.fetchmailrc changed) Both fetchall and keep on in daemon mode is a mistake! fetchmail: starting fetchmail 6.3.4 daemon and it still gets the messages and deletes them from remote server. i wonder about this behavoiur of fetchmail cause if i use IMAP than i want the messages to stay on the server, not getting them deleted! why cant i use daemon mode and the keep option? is there a possibility to fix this?? thx in advance snIP3r |
|
From: Matthias A. <mat...@gm...> - 2006-10-11 08:32:30
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, a problem with --logfile rendering it useless went undetected through the 6.3.5-beta* phase. I have uploaded fm635-daemon-logfile.patch to the BerliOS site at <http://developer.berlios.de/project/showfiles.php?group_id=1824> that is supposed to fix this problem. Feedback as to whether it really fixes - --logfile /SOME/LOG.FILE is needed. Expected behavior is that IN DAEMON MODE, output shows up in the logfile. Note you cannot use syslog at the same time. In doubt: fetchmail -q fetchmail --daemon 900 --nosyslog --logfile /SOME/LOG.FILE Please reply to fet...@li... (Reply-To set) or to fetchmail-devel@... if you have more technical comments. Kind regards, Matthias Andree -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFFLI/YvmGDOQUufZURAvv1AJsHU8McNOE7QU9tbXTy4ywtBTqyGwCgm2nA qh2SZznc+I291KTxZadpnWg= =ADSQ -----END PGP SIGNATURE----- |
|
From: Matthias A. <mat...@gm...> - 2006-10-09 08:54:14
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, I am announcing the release of fetchmail 6.3.5. This new stable version of fetchmail fixes several minor bugs and revises the FAQ. - --------------------------------------------------------------------- NOTE THAT THE CCIL.ORG MAILING LISTS ARE DEPRECATED AND WILL BE SHUT DOWN LATER THIS YEAR. Please subscribe to the new lists at <https://developer.berlios.de/mail/?group_id=1824>: - - for fetchmail-announce subscribers: subscribe to fetchmail-announce - - for fetchmail-friends subscribers: subscribe to fetchmail-users - --------------------------------------------------------------------- The software is available from: <http://developer.berlios.de/project/showfiles.php?group_id=1824&release_id=11358> The fetchmail home pages are: <http://www.fetchmail.info/> or <http://fetchmail.berlios.de/> These are the relevant changes in 6.3.5 since 6.3.4; unless otherwise noted, changes to this release were made by Matthias Andree: fetchmail 6.3.5 (released 2006-10-09): # DEPRECATED FEATURES AND MAJOR INCOMPATIBLE CHANGE ADVANCE WARNINGS * The MX and host alias DNS lookups that fetchmail performs in multidrop mode are obsolete, deprecated and may be removed from a future fetchmail version. They have never supported IPv6 (including IPv6-mapped IPv4) anyhow. Non-DNS based alias keywords such as "aka" will remain in fetchmail. * The monitor and interface options may be removed from a future fetchmail version as they are not sufficiently portable. * POP2 is obsolete. Support for POP2 may be removed from a future fetchmail version. * RPOP is obsolete, support may be removed from a future fetchmail release. * --sslcertck may become a default setting in a future fetchmail version. * The multidrop To/Cc guessing code along with the fragile duplicate suppressor is deprecated and may be removed from a future release. * The "envelope Received" option may be removed from a future release, because the Received header was never meant to be machine-readable, the format varies widely, and various other differences in behavior make parsing Received an unreliable undertaking. The enveloper option as such will remain though, in order to support Delivered-To, X-Envelope-To, X-Original-To and similar. See also <http://home.pages.de/~mandree/mail/multidrop>. * The --enable-fallback (fall back to MDA if MTA unavailable) may be removed from a future fetchmail release. * The "protocol auto" default inside fetchmail may be removed from a future fetchmail release. Explicit configuration of the protocol is recommended. * Kerberos IV support may be removed from a future fetchmail release. * SIGHUP wakeup may be removed from a future fetchmail release and cause it to terminate. * Support for operating systems that are not sufficiently POSIX compliant may be removed or operation on such systems may be suboptimal for future releases. # KNOWN BUGS AND WORKAROUNDS: (this section floats upwards through the NEWS to be on top of the list) * fetchmail does not handle messages without Message-ID header well (See sourceforge.net bug #780933) * Sun Workshop 6 (SPARC) is known to miscompile the lexer in 64-bit mode. Either compile 32-bit code or use GCC to compile 64-bit fetchmail. Note that fetchmail doesn't take advantage of 64-bit code anyways, so compiling 32-bit SPARC code should be fine. * fetchmail expects Received: headers in a particular format when parsing envelopes. * fetchmail does not track pending deletes over crashes * the command line interface is a bit narrow-minded sometimes, for instance, fetchmail -s doesn't work with a running daemon * some of the logging output is not very helpful * some of the documentation is still not up to date # BUG FIXES: * For protocols such as IMAP that are not delimited by "." lines, truncate the input buffer when the message has been completely read, to avoid taking trailing garbage into the message if the terminal CRLF is missing. Fixes Debian Bug#312415. (Patch suggested by Mike Jones, Manchester Univ.). * When using NTLM authentication, use regular IMAP response code handler after completing NTLM handshake, for robustness and consistency. (Taken from the NetBSD portable packages collection, patch-ac.) * Support Kerberos installations where krb5.h and perhaps roken.h are in .../include/krb5. Taken from NetBSD portable packages collection patch-ae. * On NetBSD, link against -lroken -lcom_err if --with-kerberos is enabled. * Drop #include <com_err.h> from Kerberos 5 header file, fixes compile error on SUSE Linux 10.0. * Fix des_pcbc_encrypt compile warnings in kerberos.c line 246. * If krb5-config provides gssapi library information, use that rather than guessing. * Improve --with-gssapi auto detection for /usr-based GSSAPI installs. * Fix --with-gssapi builds for NetBSD 3.0. * Improve KAME/getnameinfo.c portability to Linux libc5 systems. Based on a patch by Dan Fandrich. * Provide INET6 to KAME/getnameinfo.c (only useful on IPv6-enabled systems that lack getnameinfo, and there only visible in some Received: headers). Found by Dan Fandrich. * POP3: some UID flags may not be set properly on UIDL lists. (Sunil Shetye) * Make IMAP4 IDLE work on servers that do not update RECENT counts. Reported by Lars Tewes. * IMAP4 patch by Sunil Shetye: - do not depend on server updating RECENT counts at all - also enter IDLE loop when messages are present on the server. * Fix --flush description in the manual page, fetchmail does not mark messages seen unless it has successfully delivered them. Suggested by Frederic Marchal. * Fetchmail no longer attempts to stat the "-" file in daemon mode -- this is a special name to read the RC file from stdin, and cannot always be re-read anyways. BerliOS bug #7858. * When looking up ports for a service, the lookup succeeds and the returned address family isn't IPv4 or IPv6, properly free the allocated memory from the service lookup. Found by Uli Zappe. * When looking up ports for a service, only look up TCP ports. * Avoid compiling empty files, to avoid diagnostics from strict compilers. * If the lockfile ends before the process ID, treat it as stale and unlink it. Reported by Justin Pryzby, Debian Bug #376603. * SIGHUP wake-up behavior was broken since 5.9.13's Cygwin changes, in that for non-root users, SIGHUP would abort the first poll and subsequently interfere with new polls, and SIGHUP would be ignored for root users. SIGHUP now matches documented behavior. SIGUSR1 has always been a wakeup signal for both root (undocumented) and non-root users. See also the deprecation warning above. * Track getaddrinfo() results to properly free them after timeouts and make sure that getaddrinfo() isn't interrupted by a timeout (which breaks on MacOS X), reported by Uli Zappe. This should fix Debian Bug#294547 and Bug#377135. * --logfile is now handled more carefully, errors opening the logfile are now reported to the TTY where fetchmail was started from. * fetchmail now complains and aborts when it cannot properly daemonize itself. * fix compilation on systems that don't know struct addrinfo (Solaris 2.6). * ignore SIGPIPE signals and rely on functions to return EPIPE instead. This is necessary because the former longjmp() from the signal handler is unsafe and makes the whole fetchmail behavior undefined after the event. * Avoid crash in env.c/host_fqdn if we cannot canonicalize our own hostname. Reported by Alexander Holler. * SSL fix by Miloslav Trmac (Red Hat): free the SSL contexts after the connection, to avoid from growing SSL certpaths without bounds, avoid using SSL contexts for unrelated connections, and to fix Red Hat Bug #206346. # CHANGES: * Rename all fetchmail-internal lock_* functions to fm_lock_*. Obsoletes NetBSD portable packages collection patch-ah, patch-ai and patch-aj. * Configure prints a warning (but proceeds) if Kerberos IV support is enabled. * In verbose mode, log every IP fetchmail tries to connect to, to avoid misleading the user. Suppress EAFNOSUPPORT errors from socket() call, too. Fixes Debian Bug #361825, reported by Daniel Baur. * In idle mode, fetchmail complains about the fetchall option. * When a connection fails, log not only the IP address, but also host and service name and the port number. Log the latter when trying to connect in verbose mode, too. * Keep syslog output at one line per message (this works if no errors occur). * Fetchmail in verbose mode now logs if it opportunistically upgrades a POP3 or IMAP connection to TLS security with STLS/STARTTLS. * fetchmail now supports fo...@ex...=bar user mappings for multidrop boxes. * switch setjmp/longjmp to sigsetjmp/siglongjmp * IMAP now supports the EXTERNAL authentication method, courtesy of Götz 'nimrill' Babin-Ebell, BerliOS patch #1095 with minor changes. * The sslproto keywords are now case insensitive, courtesy of Götz 'nimrill' Babin-Ebell, BerliOS patch #1095. * When going to sleep, log for how long. Suggested by Claudia Ludwig. * When the server name cannot be canonicalized, log the gai_strerror value. # TRANSLATION UPDATES: * Catalan/ca (Ernest Adrogué Calveras), Japanese/ja (Takeshi Hamasaki) - also made gettext 0.15 ready, Polish/pl (Jakub Bogusz), Russian/ru (Pavel Maryanov), Spanish/es (Héctor García Álvarez), Vietnamese/vi (Clytie Siddall) # CONTRIBUTED SCRIPTS: * PopDel.py was revised by Joshua Crawford to display the From: address and list every email, even if it has no Subject: header; and not delete the wrong message in the presence of mail without Subject: headers. Regards, - -- Matthias Andree -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFFKfHwvmGDOQUufZURAgKqAKDKa6mUkNnJGMjXMSupaL9u5oCSzwCbBv+C G+3g7/T/1Rteh1hSP2TCDeA= =oOOH -----END PGP SIGNATURE----- |
|
From: Matthias A. <mat...@gm...> - 2006-10-06 01:20:54
|
Michelle Konzack schrieb am 2006-10-01: > Wha not install procmail and configure it as MDA for fetchmail? Because procmail is an unmaintained piece of unconfigurable software (to many at least) and even such simple recipes are usually wrong - yours for instance destroys envelope information and is up to nice forwarding loops... -- Matthias Andree |
|
From: Andrea B. <and...@ti...> - 2006-10-04 18:15:37
|
> poll mail.tin.it proto pop3 user 'andrea' with password 'mypassword' > to andrea smtphost server/2345 It's working. Thank Andrea |
|
From: Rob M. <rob...@gm...> - 2006-10-02 20:52:59
|
On 10/2/06, Andrea Bencini <and...@ti...> wrote: > In .fetchmailrc file how and where can I put the option "smtphost > serve/2345"? Clearly documented in the man page. > For example, in .fetcmailrc file I have this string > poll mail.tin.it proto pop3 user 'andrea' with password 'mypassword' to > andrea1 > > Can I put that option? and what is the form to put it? The man page specifies it as a user option, so (unchecked): poll mail.tin.it proto pop3 user 'andrea' with password 'mypassword' to andrea smtphost server/2345 Should work -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche |
|
From: Andrea B. <and...@ti...> - 2006-10-02 18:42:57
|
> Shouldn't make a difference if you're doing it properly. > Postfix runs postalias on the $alias_databases if you type "newaliases"... :-) Thank you for this info. Andrea |
|
From: Andrea B. <and...@ti...> - 2006-10-02 18:40:03
|
In .fetchmailrc file how and where can I put the option "smtphost serve/2345"? For example, in .fetcmailrc file I have this string poll mail.tin.it proto pop3 user 'andrea' with password 'mypassword' to andrea1 Can I put that option? and what is the form to put it? Thank Andrea |
|
From: Jakob H. <jh...@pl...> - 2006-10-02 18:25:10
|
Quoting Weidong Cui: > 33 messages for cu...@in... at my.inbox.com (119345 octets). > fetchmail: POP3> LIST 1 So inbox.com's POP3 is not compliant to RFC1939. fetchmail could work around that (not hard to do that), but I'm not sure if we should really work around all kinds of brokenness. OTOH, taking a glance at pop3.c, I'd say the code is already there... |
|
From: Weidong C. <cu...@in...> - 2006-10-02 17:12:16
|
Thanks, I did it as you said, ( fetchmail -a , and add "options fetchall" in my config file). but it output: fetchmail: 6.3.4 querying my.inbox.com (protocol POP3) at Mon Oct 2 17:23:10 2006: poll started fetchmail: POP3< +OK WM29.inbox.com POP3 server ready <386...@WM...> fetchmail: POP3> CAPA fetchmail: POP3< +OK Capability list follows fetchmail: POP3< USER fetchmail: POP3< SASL CRAM-MD5 fetchmail: POP3< UIDL fetchmail: POP3< APOP fetchmail: POP3< . fetchmail: POP3> AUTH CRAM-MD5 fetchmail: POP3< + PDAyMzU5OTM0MDdCNEM4MDhAV00yOS5pbmJveC5jb20+ fetchmail: decoded as <023...@WM...> fetchmail: POP3> Y3Vpd2RAaW5ib3guY29tIDQ5NzJmNDg0ZTYyOGUyODM5MDBkZGRlYjQ3YTJhNzU0 fetchmail: POP3< +OK Authentication successful fetchmail: selecting or re-polling default folder fetchmail: POP3> STAT fetchmail: POP3< +OK 33 119345 33 messages for cu...@in... at my.inbox.com (119345 octets). fetchmail: POP3> LIST 1 fetchmail: POP3< -ERR error during operation fetchmail: POP3> QUIT fetchmail: POP3< +OK WM29.inbox.com POP3 server signing off fetchmail: 6.3.4 querying my.inbox.com (protocol POP3) at Mon Oct 2 17:23:15 2006: poll completed fetchmail: Query status=4 (PROTOCOL) fetchmail: Deleting fetchids file. fetchmail: normal termination, status 4 fetchmail: Deleting fetchids file. > -----Original Message----- > From: jh...@pl... > Sent: Mon, 02 Oct 2006 14:52:59 +0200 > To: cu...@in... > Subject: Re: [fetchmail-users] how to config fetchmail for www.inbox.com > email > > Quoting Weidong Cui: > >> fetchmail: POP3> TOP 1 99999999 >> fetchmail: POP3< -ERR Syntax error, command unrecognized > > use the "fetchall" option to make fetmail use RETR instead if the > default TOP. > > Hm, TOP is an optional POP3 command (even though strongly encouraged by > the RFC), so maybe fetchmail should fall back if it's not working... or > use RETR by default, using TOP by default is stupid, IMO... |
|
From: Jakob H. <jh...@pl...> - 2006-10-02 15:05:55
|
Quoting Weidong Cui: Oh, and please put a note at the top of your mails about the C/R-system you are using, so I won't waste my time by reading them... |
|
From: Jakob H. <jh...@pl...> - 2006-10-02 14:53:34
|
Quoting Weidong Cui: > fetchmail: POP3> TOP 1 99999999 > fetchmail: POP3< -ERR Syntax error, command unrecognized use the "fetchall" option to make fetmail use RETR instead if the default TOP. Hm, TOP is an optional POP3 command (even though strongly encouraged by the RFC), so maybe fetchmail should fall back if it's not working... or use RETR by default, using TOP by default is stupid, IMO... |
|
From: Weidong C. <cu...@in...> - 2006-10-02 14:27:04
|
Hi, All, I have a email account at www.inbox.com, but I can not use fetchmail to received my email from there. Belowed are informations for my fetchmail configuration and running output. So I read my email via webpage now. Thanks in advance. Weidong Cui cu...@in... Mon Oct 2 14:08:30 UTC 2006 ******************************************************************************** My .fetchmailrc file: # Configuration created Fri Sep 29 20:37:49 2006 by fetchmailconf 1.52 $Revision: 4740 $ set postmaster "weidong" set bouncemail set no spambounce set properties "" poll my.inbox.com proto pop3 and options no dns user 'cu...@in...' there with password 'passwordxxxxx' is 'weidong' here fetchmail: 6.3.4 querying my.inbox.com (protocol POP3) at Mon Oct 2 14:12:43 2006: poll started fetchmail: POP3< +OK WM29.inbox.com POP3 server ready <386...@WM...> fetchmail: POP3> CAPA fetchmail: POP3< +OK Capability list follows fetchmail: POP3< USER fetchmail: POP3< SASL CRAM-MD5 fetchmail: POP3< UIDL fetchmail: POP3< APOP fetchmail: POP3< . fetchmail: POP3> AUTH CRAM-MD5 fetchmail: POP3< + PDY4MDM0OUE3RjFCM0M4MDhAV00yOS5pbmJveC5jb20+ fetchmail: POP3> Y3Vpd2RAaW5ib3guY29tIGY4MWRhNjZiZGVmNDQ5YTgzNzhlOWQ3YzZmN2VmYmQx fetchmail: POP3< +OK Authentication successful fetchmail: POP3> STAT fetchmail: POP3< +OK 30 101088 fetchmail: POP3> LAST fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: POP3> UIDL fetchmail: POP3< +OK unique-id listing follows fetchmail: POP3< 1 19 fetchmail: POP3< 2 21 fetchmail: POP3< 3 23 fetchmail: POP3< 4 28 fetchmail: POP3< 5 31 fetchmail: POP3< 6 33 fetchmail: POP3< 7 34 fetchmail: POP3< 8 35 fetchmail: POP3< 9 36 fetchmail: POP3< 10 37 fetchmail: POP3< 11 38 fetchmail: POP3< 12 39 fetchmail: POP3< 13 40 fetchmail: POP3< 14 41 fetchmail: POP3< 15 42 fetchmail: POP3< 16 43 fetchmail: POP3< 17 44 fetchmail: POP3< 18 45 fetchmail: POP3< 19 48 fetchmail: POP3< 20 50 fetchmail: POP3< 21 54 fetchmail: POP3< 22 55 fetchmail: POP3< 23 57 fetchmail: POP3< 24 58 fetchmail: POP3< 25 60 fetchmail: POP3< 26 68 fetchmail: POP3< 27 69 fetchmail: POP3< 28 71 fetchmail: POP3< 29 76 fetchmail: POP3< 30 77 fetchmail: POP3< . 30 messages for cu...@in... at my.inbox.com (101088 octets). fetchmail: POP3> LIST 1 fetchmail: POP3< +OK 1 1086 fetchmail: POP3> TOP 1 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:1 (1086 octets) fetchmail: POP3> LIST 2 fetchmail: POP3< +OK 2 4863 fetchmail: POP3> TOP 2 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:2 (4863 octets) fetchmail: POP3> LIST 3 fetchmail: POP3< +OK 3 1910 fetchmail: POP3> TOP 3 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:3 (1910 octets) fetchmail: POP3> LIST 4 fetchmail: POP3< +OK 4 3888 fetchmail: POP3> TOP 4 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:4 (3888 octets) fetchmail: POP3> LIST 5 fetchmail: POP3< +OK 5 8147 fetchmail: POP3> TOP 5 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:5 (8147 octets) fetchmail: POP3> LIST 6 fetchmail: POP3< +OK 6 2100 fetchmail: POP3> TOP 6 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:6 (2100 octets) fetchmail: POP3> LIST 7 fetchmail: POP3< +OK 7 2699 fetchmail: POP3> TOP 7 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:7 (2699 octets) fetchmail: POP3> LIST 8 fetchmail: POP3< +OK 8 5581 fetchmail: POP3> TOP 8 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:8 (5581 octets) fetchmail: POP3> LIST 9 fetchmail: POP3< +OK 9 2733 fetchmail: POP3> TOP 9 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:9 (2733 octets) fetchmail: POP3> LIST 10 fetchmail: POP3< +OK 10 2574 fetchmail: POP3> TOP 10 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:10 (2574 octets) fetchmail: POP3> LIST 11 fetchmail: POP3< +OK 11 2272 fetchmail: POP3> TOP 11 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:11 (2272 octets) fetchmail: POP3> LIST 12 fetchmail: POP3< +OK 12 2619 fetchmail: POP3> TOP 12 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:12 (2619 octets) fetchmail: POP3> LIST 13 fetchmail: POP3< +OK 13 2141 fetchmail: POP3> TOP 13 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:13 (2141 octets) fetchmail: POP3> LIST 14 fetchmail: POP3< +OK 14 3577 fetchmail: POP3> TOP 14 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:14 (3577 octets) fetchmail: POP3> LIST 15 fetchmail: POP3< +OK 15 3430 fetchmail: POP3> TOP 15 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:15 (3430 octets) fetchmail: POP3> LIST 16 fetchmail: POP3< +OK 16 2461 fetchmail: POP3> TOP 16 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:16 (2461 octets) fetchmail: POP3> LIST 17 fetchmail: POP3< +OK 17 2145 fetchmail: POP3> TOP 17 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:17 (2145 octets) fetchmail: POP3> LIST 18 fetchmail: POP3< +OK 18 5079 fetchmail: POP3> TOP 18 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:18 (5079 octets) fetchmail: POP3> LIST 19 fetchmail: POP3< +OK 19 3480 fetchmail: POP3> TOP 19 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:19 (3480 octets) fetchmail: POP3> LIST 20 fetchmail: POP3< +OK 20 2166 fetchmail: POP3> TOP 20 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:20 (2166 octets) fetchmail: POP3> LIST 21 fetchmail: POP3< +OK 21 2123 fetchmail: POP3> TOP 21 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:21 (2123 octets) fetchmail: POP3> LIST 22 fetchmail: POP3< +OK 22 2280 fetchmail: POP3> TOP 22 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:22 (2280 octets) fetchmail: POP3> LIST 23 fetchmail: POP3< +OK 23 4069 fetchmail: POP3> TOP 23 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:23 (4069 octets) fetchmail: POP3> LIST 24 fetchmail: POP3< +OK 24 4070 fetchmail: POP3> TOP 24 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:24 (4070 octets) fetchmail: POP3> LIST 25 fetchmail: POP3< +OK 25 8202 fetchmail: POP3> TOP 25 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:25 (8202 octets) fetchmail: POP3> LIST 26 fetchmail: POP3< +OK 26 2249 fetchmail: POP3> TOP 26 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:26 (2249 octets) fetchmail: POP3> LIST 27 fetchmail: POP3< +OK 27 2249 fetchmail: POP3> TOP 27 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:27 (2249 octets) fetchmail: POP3> LIST 28 fetchmail: POP3< +OK 28 2496 fetchmail: POP3> TOP 28 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:28 (2496 octets) fetchmail: POP3> LIST 29 fetchmail: POP3< +OK 29 4344 fetchmail: POP3> TOP 29 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:29 (4344 octets) fetchmail: POP3> LIST 30 fetchmail: POP3< +OK 30 4055 fetchmail: POP3> TOP 30 99999999 fetchmail: POP3< -ERR Syntax error, command unrecognized fetchmail: Syntax error, command unrecognized fetchmail: couldn't fetch headers, message cu...@in...@my.inbox.com:30 (4055 octets) fetchmail: POP3> QUIT fetchmail: POP3< +OK WM29.inbox.com POP3 server signing off fetchmail: 6.3.4 querying my.inbox.com (protocol POP3) at Mon Oct 2 14:13:37 2006: poll completed fetchmail: normal termination, status 1 |
|
From: Michelle K. <lin...@fr...> - 2006-10-02 13:48:13
|
Wha not install procmail and configure it as MDA for fetchmail?
Then add the following singel recipe to your ~/.procmailrc
:0
! you...@gm...
Greetings
Michelle Konzack
Systemadministrator
Tamay Dogan Network
Debian GNU/Linux Consultant
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack Apt. 917 ICQ #328449886
50, rue de Soultz MSM LinuxMichi
0033/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com)
|
|
From: Michelle K. <lin...@fr...> - 2006-10-02 13:48:00
|
Am 2006-09-30 17:48:49, schrieb M. Fioretti:
> Being too clever for my own good, I have the home computer in such a
> state, thanks to a lot of experiments, that I cannot install other
> clients without a lot of work (my fault, yes). However, I have the
???
I see you are using mutt 1.5.9 so why not try
imaps://you...@se...d
imap://you...@se...d
pop3://you...@se...d
Greetings
Michelle Konzack
Systemadministrator
Tamay Dogan Network
Debian GNU/Linux Consultant
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack Apt. 917 ICQ #328449886
50, rue de Soultz MSM LinuxMichi
0033/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com)
|
|
From: Rob M. <rob...@gm...> - 2006-09-30 22:33:49
|
On 9/30/06, M. Fioretti <mfi...@mc...> wrote:
> Here is the log:
>
> Sep 30 15:04:19 fm dovecot: Dovecot v1.0.rc7 starting up
> Sep 30 15:04:22 fm dovecot: auth(default): passwd-file /etc/dovecot_user_file: Read 1 users
> Sep 30 15:05:05 fm dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAPsecured lip=::ffff:SERVER_IP_HERE rip=::ffff:CLient_IP_HERE resp=LONG_STRING_HERE VDBB
> Sep 30 15:05:05 fm dovecot: auth(default): passwd-file(user_name,::ffff:CLIENT_IP_HERE): unknown user
> Sep 30 15:05:07 fm dovecot: auth(default): client out: FAIL 1 user=user_name
> Sep 30 15:05:07 fm dovecot: imap-login: Aborted login: user=<user_name>, method=PLAIN, rip=::ffff:CLIENT_IP_HERE, lip=::ffff:SERVER_IP_HERE, TLS
Now, repeat with squirrelmail - I suspect you'll ffind either that
squirrelmail isn't using PLAIN, or is but not using TLS. Worth
checking that you've allowed PLAIN in the auth methods for dovecot.
Alternatively, you're authenticating this with SASL and you need to
set the correct domain for authentication.
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche
|
|
From: M. F. <mfi...@mc...> - 2006-09-30 22:15:09
|
On Sat, Sep 30, 2006 21:30:52 PM +0200, Matthias Andree (mat...@gm...) wrote: > > of course, but the password should be the same, shouldn't it? > > That depends on Dovecot configuration and is outside the scope of the > fetchmail lists. > Anyways, see <http://www.fetchmail.info/fetchmail-FAQ.html#K6> just tried. sslproto ssl23 doesn't change anything. In any case, I had already signalled the problem both here and on the dovecot list, since I didn't know where to start from and, for all I know, I could have made errors on both sides. Still not sure that that is not the case... Ciao, Marco -- Marco Fioretti mfioretti, at the server mclink.it Fedora Core 3 for low memory http://www.rule-project.org/ Needs are a function of what other people have. |
|
From: M. F. <mfi...@mc...> - 2006-09-30 21:58:16
|
On Sat, Sep 30, 2006 17:38:37 PM +0100, Rob MacGregor (rob...@gm...) wrote: > Yes, but my point is that dovecot does not necessarily accept the > authentication method that fetchmail is trying to use from a remote > host (or even a local one). > > I would advise you do the following: > > 1) Increase the logging level on the dovecot server. That will tell > you why the connection is failing. Done, see result below. Comments are welcome. THanks a lot also for suggesting this: > 2) Install fetchmail locally on the dovecot server. Try doing a > mail check both against localhost and it's external IP. I'll do it tomorrow, if still needed (must really leave the keyboard now). Here is the log: Sep 30 15:04:19 fm dovecot: Dovecot v1.0.rc7 starting up Sep 30 15:04:22 fm dovecot: auth(default): passwd-file /etc/dovecot_user_file: Read 1 users Sep 30 15:05:05 fm dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAPsecured lip=::ffff:SERVER_IP_HERE rip=::ffff:CLient_IP_HERE resp=LONG_STRING_HERE VDBB Sep 30 15:05:05 fm dovecot: auth(default): passwd-file(user_name,::ffff:CLIENT_IP_HERE): unknown user Sep 30 15:05:07 fm dovecot: auth(default): client out: FAIL 1 user=user_name Sep 30 15:05:07 fm dovecot: imap-login: Aborted login: user=<user_name>, method=PLAIN, rip=::ffff:CLIENT_IP_HERE, lip=::ffff:SERVER_IP_HERE, TLS TIA, Marco |
|
From: Matthias A. <mat...@gm...> - 2006-09-30 21:32:27
|
"Andrea Bencini" <and...@ti...> writes: >> Good, just remember to run "newaliases" > > I run "postalias" because I have "postfix". Shouldn't make a difference if you're doing it properly. Postfix runs postalias on the $alias_databases if you type "newaliases"... :-) -- Matthias Andree |
|
From: Matthias A. <mat...@gm...> - 2006-09-30 21:31:26
|
"M. Fioretti" <mfi...@mc...> writes: > What else could it be? > >> (Note that using squirrelmail doesn't necessarily test the same >> connection methods, > > of course, but the password should be the same, shouldn't it? That depends on Dovecot configuration and is outside the scope of the fetchmail lists. Anyways, see <http://www.fetchmail.info/fetchmail-FAQ.html#K6> -- Matthias Andree |
|
From: Rob M. <rob...@gm...> - 2006-09-30 21:31:26
|
On 9/30/06, Spam Me <wel...@gm...> wrote:
> Hello,
> I appologize if this has been asked before, but I've search the archives and
> found no solution.
Well, output of "fetchmail -v -v -v" would be useful so we can work
out where it's going wrong. You may also need to set smtpaddress and
provide a delivery destination in the poll line.
Output of "fetchmail --configdump" to show what fetchmail thinks of
your config would be handy too - don't forget to munge passwords.
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche
|
|
From: Matthias A. <mat...@gm...> - 2006-09-30 21:29:31
|
Marco Fioretti <mfi...@mc...> writes: > Hello, > > I have dovecot q1.0-0_22.rc7 up and running on a server: I can read > email from squirrelmail just fine. When I try to download email with > fetchmail, however, I get the result below. Why is that happening? In > dovecot.conf I have: > > protocols = imap imaps pop3, > > so why should pop3 or imap fail? Because Dovecot offers TLS (STLS/STARTTLS) and fetchmail uses it.. > fetchmail: POP3> STLS > fetchmail: POP3< +OK Begin TLS negotiation now. > fetchmail: IMAP> A0003 CAPABILITY > fetchmail: IMAP< * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDRE > N NAMESPACE LOGIN-REFERRALS AUTH=PLAIN AUTH=DIGEST-MD5 > fetchmail: IMAP< A0003 OK Capability completed. > fetchmail: Protocol identified as IMAP4 rev 1 > fetchmail: IMAP> A0004 LOGIN "user_name" * > fetchmail: IMAP< A0004 NO Authentication failed. > fetchmail: IMAP> A0005 * Whatever this is. Something's wrong here, but I'm not going to look at 6.3.2. -- Matthias Andree |
|
From: Matthias A. <mat...@gm...> - 2006-09-30 21:27:03
|
"Spam Me" <wel...@gm...> writes: > Hello, > I appologize if this has been asked before, but I've search the archives and found no solution. > > What I'd like to do is have fetchmail collect mail from all my various email accounts, and forward everything to my gmail account. I've > been able to get the polling working properly, however I can't get the messages properly forwarding to my gmail account. I was just > wondering if I've set the smtp variables correctly (see .fetchmailrc included below)? If i remove the two smtp lines, fetchmail happily > runs and exits with no errors (however since I dont have any email software installed locally the mail doesn't actually go anywhere). > However, when I add the smtp lines the software hangs on the "reading message add...@gm...@gmail-pop.l.google.com:1 of 11 (2020 > octets)" line. Please see http://www.fetchmail.info/fetchmail-FAQ.html#G3 -- and don't post HTML to lists. -- Matthias Andree |
18 messages has been excluded from this view by a project administrator.
