Prev: Best practice to drop spam with virtual mailboxes
Next: Restrict alias delivery to internal users
From: Uwe Dippel on 12 May 2010 05:58
This is quite strange:

I have been running fetchmail from a cronjob for a few years now, to
collect my messages from an IMAP server and forward it to another one.

This was and is the (only) cronjob:
# m h dom mon dow command
5 * * * * /usr/bin/fetchmail > /dev/null
No changes of the .fetchmailrc, neither. Only, since I installed
(k)ubuntu 10.04, regularly fetchmail cannot .forward the messages
whenever it is called at the full hour plus 5 minutes (e.g. 11:05,
12:05), because postfix seems unavailable:
"fetchmail: connection to localhost:smtp [::1/25] failed: Connection
refused." is what I get in the mail at *:05.

postconf -n:
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
default_transport = smtp
inet_interfaces = all
inet_protocols = ipv4
mailbox_size_limit = 102400000
mydestination = example.com, mybox, localhost.localdomain, localhost
myhostname = mybox.example.com
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
myorigin = /etc/mailname
readme_directory = no
recipient_delimiter =
relay_transport = smtp
relayhost =
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtpd_use_tls = yes
(but I guess nothing wrong here, since at all other times it works fine)

Here is the postfix log for the same minute when fetchmail couldn't
connect as above:
May 12 11:05:01 example postfix/smtpd[5183]: connect from
localhost[127.0.0.1]
May 12 11:05:01 example postfix/smtpd[5183]: 9AFC694118E:
client=localhost[127.0.0.1]
May 12 11:05:01 example postfix/cleanup[5187]: 9AFC694118E:
message-id=<bdbcaa51093724499dc38ed6001728d8(a)pacific-conferences.com>
May 12 11:05:01 example postfix/qmgr[1281]: 9AFC694118E:
from=<marketing.my(a)pacific-conferences.com>, size=23920, nrcpt=1 (queue
active)
May 12 11:05:01 example postfix/cleanup[5187]: BB1B2941191:
message-id=<bdbcaa51093724499dc38ed6001728d8(a)pacific-conferences.com>
May 12 11:05:01 example postfix/smtpd[5183]: disconnect from
localhost[127.0.0.1]
May 12 11:05:01 example postfix/local[5189]: 9AFC694118E:
to=<udippel(a)localhost>, relay=local, delay=0.23,
delays=0.14/0.01/0/0.09, dsn=2.0.0, status=sent (forwarded as BB1B2941191)
May 12 11:05:01 example postfix/qmgr[1281]: BB1B2941191:
from=<marketing.my(a)pacific-conferences.com>, size=24059, nrcpt=1 (queue
active)
May 12 11:05:01 example postfix/qmgr[1281]: 9AFC694118E: removed
May 12 11:05:01 example postfix/pickup[4738]: DEBF794118E: uid=1000
from=<udippel>
May 12 11:05:01 example postfix/cleanup[5187]: DEBF794118E:
message-id=<20100512030501.DEBF794118E(a)example.mybox.example.com>
May 12 11:05:02 example postfix/qmgr[1281]: DEBF794118E:
from=<udippel(a)example.mybox.example.com>, size=650, nrcpt=1 (queue active)
May 12 11:05:02 example postfix/cleanup[5187]: 01974940ACA:
message-id=<20100512030501.DEBF794118E(a)example.mybox.example.com>
May 12 11:05:02 example postfix/local[5189]: DEBF794118E:
to=<udippel(a)example.mybox.example.com>, orig_to=<udippel>, relay=local,
delay=0.48, delays=0.42/0/0/0.06, dsn=2.0.0, status=sent (forwarded as
01974940ACA)
May 12 11:05:02 example postfix/qmgr[1281]: DEBF794118E: removed
May 12 11:05:02 example postfix/qmgr[1281]: 01974940ACA:
from=<udippel(a)example.mybox.example.com>, size=805, nrcpt=1 (queue active)
May 12 11:05:02 example postfix/smtp[5191]: 01974940ACA:
to=<udippel(a)mymta.example.com>, orig_to=<udippel>,
relay=mymta.example.com[172.16.0.4]:25, delay=0.13,
delays=0.06/0.01/0.04/0.02, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued
as 2208B186)
May 12 11:05:02 example postfix/qmgr[1281]: 01974940ACA: removed
May 12 11:05:03 example postfix/smtp[5190]: BB1B2941191:
to=<udippel(a)mymta.example.com>, orig_to=<udippel(a)localhost>,
relay=mymta.example.com[172.16.0.4]:25, delay=1.3,
delays=0.08/0.01/0.01/1.2, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued
as 14C38186)
May 12 11:05:03 example postfix/qmgr[1281]: BB1B2941191: removed

Can anyone help me to explain what has been going on, since I installed
Ubuntu 10.04?

Uwe

From: Wietse Venema on 12 May 2010 07:13
> "fetchmail: connection to localhost:smtp [::1/25] failed: Connection
> refused." is what I get in the mail at *:05.

Fetchmail wants to connect over IP VERSION 6.

Apparently, Postfix does not listen on IP VERSION 6.

Wietse

From: Uwe Dippel on 12 May 2010 09:19
On 05/12/2010 07:13 PM, Wietse Venema wrote:
>> "fetchmail: connection to localhost:smtp [::1/25] failed: Connection
>> refused." is what I get in the mail at *:05.
>>
> Fetchmail wants to connect over IP VERSION 6.
>
> Apparently, Postfix does not listen on IP VERSION 6.
>

Apparently.
Maybe I should ask on a fetchmail list, why fetchmail always and only 5
minutes past the hour tries to connect over IPv6!?

Thanks anyway,

Uwe

From: Jorge Andrea G Carminati on 12 May 2010 09:27
> -----Original Message-----
> From: owner-postfix-users(a)postfix.org [mailto:owner-postfix-
> users(a)postfix.org] On Behalf Of Uwe Dippel
> Sent: Wednesday, May 12, 2010 10:20
> To: Wietse Venema
> Cc: postfix-users(a)postfix.org
> Subject: Re: postfix unavailable at 5 minutes after the hour?
>
> On 05/12/2010 07:13 PM, Wietse Venema wrote:
> >> "fetchmail: connection to localhost:smtp [::1/25] failed: Connection
> >> refused." is what I get in the mail at *:05.
> >>
> > Fetchmail wants to connect over IP VERSION 6.
> >
> > Apparently, Postfix does not listen on IP VERSION 6.
> >
>
> Apparently.
> Maybe I should ask on a fetchmail list, why fetchmail always and only 5
> minutes past the hour tries to connect over IPv6!?
>
> Thanks anyway,
>
> Uwe
>
>

Uwe: you may want to try this tip that I've got from google: http://www.bloovis.com/wordpress/?p=172
HTH

"Cuidar la naturaleza es vivir mejor... hag?moslo juntos. Imprime s?lo lo necesario."

"La informaci?n transmitida en este mensaje est? destinada ?nicamente a la persona o entidad a la cual el mismo est? dirigido, y puede contener material confidencial, reservado o sujeto al secreto profesional. Cualquier revisi?n, retransmisi?n, divulgaci?n u otro uso de la misma, o la realizaci?n de cualquier acci?n basada en ella por personas o entidades distintas de la indicada, no est? permitida. Si usted ha recibido este mensaje por error, tenga la amabilidad de destruirlo, sin copiarlo ni divulgar su contenido. Muchas gracias."


The information contained in this message is directed exclusively to the person or entity to whom the message is addressed, and it might contain information that is confidential, privileged or otherwise legally exempt from disclosure. Any action based on it, performed by an individual or entity different from the one it was intended, is not allowed and its contents should not be read, forwarded, disclosed, or used in any other way. If you have received it by mistake please delete it from your system, you should also not copy the message nor disclose its contents to anyone. Thank you.

From: Wietse Venema on 12 May 2010 09:39
Uwe Dippel:
> On 05/12/2010 07:13 PM, Wietse Venema wrote:
> >> "fetchmail: connection to localhost:smtp [::1/25] failed: Connection
> >> refused." is what I get in the mail at *:05.
> >>
> > Fetchmail wants to connect over IP VERSION 6.
> >
> > Apparently, Postfix does not listen on IP VERSION 6.
> >
>
> Apparently.
> Maybe I should ask on a fetchmail list, why fetchmail always and only 5
> minutes past the hour tries to connect over IPv6!?

It is only speculation, but perhaps fetchmail uses IPv6 because
you have a record with:

::1 localhost ...

in /etc/hosts. That would explain why fetchmail tries to use that
information. Of course it is not very nice that fetchmail spams
you with error messages for this.

So the "solution" is to nuke this entry from /etc/hosts or to turn
on IPv6 support in Postfix (inet_protocols = all).

Wietse

 |  Next  |  Last
Pages: 1 2
Prev: Best practice to drop spam with virtual mailboxes
Next: Restrict alias delivery to internal users