Re: mynetworks support for ipv6 link local (fe80) hosts

2012-06-02 Thread Wietse Venema
Derek Atkins:
 Viktor Dukhovni postfix-us...@dukhovni.org writes:
 
  On Fri, Jun 01, 2012 at 12:35:54PM -0400, Derek Atkins wrote:
 
   mynetworks = 127.0.0.0/8 1.2.3.4/24 192.168.1.0/24 [2001:1234:1234::]/48
   [fe80::]/10 [fe80::%eth0]/10 [::1]/128
  
  Yes, I have.  In fact that was the first thing I tried, but it didn't
  work.  I added the interface descriptor on the theory that it was
  outputting it so therefore it might want it.  Obviously that didn't
  help, either.

Postfix has never output interface descriptor information unless some
helpful port maintainer added support to 'improve' this.

  See http://archives.neohapsis.com/archives/postfix/2010-11/thread.html#295
  Postfix does not AFAIK support link-local address scopes.
 
 For the record, this appears to have been fixed somewhere between 2.7
 and 2.9; I just backported 2.9.2 to my mail server and using
 mynetworks = [fe80::]/10 works as I would expect it to.

Postfix has always wortked this way unless some helpful port maintainer 
added support to break this.

Wietse


AOL declines mails with 421dnsnr on one of our nodes

2012-06-02 Thread Christian Parpart
Hi all,

I am about to mvoe our postfix MTAs from physical nodes into virtual nodes,
as they're just transmitting and we're not receiving mails on these
postfix'es anyways,
I thought it might be not that an overhead, however, everyone seems to
accept
the mails from our new VM postfix node except AOL, responding with
an error code [1].

No matter how often I am to read this text, I still don't get what they
actually want from me.
We've properly set up DNS (name-to-IP and reverse IP-to-name).

In the logs, I see a message like this:

(delivery temporarily suspended: host mailin-02.mx.aol.com[64.12.139.193]
refused to talk to me: 421 4.7.1 :
(DNS:NR) http://postmaster.info.aol.com/errors/421dnsnr.html)

Does anyone know what I might have been missing in my config? Well, the
config file looks
almost the very same as on the physical nodes, it's just, that the VM
doesn't have a direct public IP now.
But the outgoing IP is set up with DNS properly, however.

Many thanks in advance,
Christian Parpart.

[1] http://postmaster.info.aol.com/errors/421dnsnr.html


Re: AOL declines mails with 421dnsnr on one of our nodes

2012-06-02 Thread Wietse Venema
Christian Parpart:
 But the outgoing IP is set up with DNS properly, however.

You have told everything but the IP address, so how can we help?

Wietse


[OT] frequent TRY_AGAINs and 10s timeouts, but *only* with b.barracudacentral.org

2012-06-02 Thread Sahil Tandon
I am seeing hundreds (on higher volume days, over a thousand) of lines
like:

 Jun  2 10:04:30 mx1 postfix/dnsblog[58868]: warning: dnsblog_query:
 lookup error for DNS query 23.124.167.115.b.barracudacentral.org: Host
 or domain name not found. Name service error for
 name=23.124.167.115.b.barracudacentral.org type=A: Host not found, try
 again
 
 Jun  2 10:04:33 mx1 postfix/smtpd[89019]: warning:
 17.204.24.8.b.barracudacentral.org: RBL lookup error: Host or domain
 name not found. Name service error for
 name=17.204.24.8.b.barracudacentral.org type=A: Host not found, try
 again

 Jun  2 10:04:37 mx1 postfix/postscreen[55753]: warning: dnsblog reply
 timeout 10s for b.barracudacentral.org

These lines are interspersed among others that indicate more normal
activity with b.barracudacentral.org, e.g.:

 Jun  2 10:04:10 mx1 postfix/dnsblog[55985]: addr 199.30.50.35 listed by domain 
b.barracudacentral.org as 127.0.0.2
 Jun  2 10:04:47 mx1 postfix/dnsblog[66369]: addr 157.56.112.23 listed by 
domain b.barracudacentral.org as 127.0.0.2

I know this is not an issue with Postfix (which dutifully reports the
TRY_AGAIN it receives from the system library), but I wonder if anyone
else is seeing this from barracuda?  Based on a week's worth of logs, I
do not see even a single instance of this problem with any other RBL
(and we query several).

I've separately engaged our DNS admins in case they could offer some
insight, but it would be interesting to learn if others are experiencing
the same issue /only/ with barracuda. 

-- 
Sahil Tandon


Re: [OT] frequent TRY_AGAINs and 10s timeouts, but *only* with b.barracudacentral.org

2012-06-02 Thread Rod K

Yes, I've seen that this week as well.

On 6/2/2012 12:44 PM, Sahil Tandon wrote:

I am seeing hundreds (on higher volume days, over a thousand) of lines
like:

  Jun  2 10:04:30 mx1 postfix/dnsblog[58868]: warning: dnsblog_query:
  lookup error for DNS query 23.124.167.115.b.barracudacentral.org: Host
  or domain name not found. Name service error for
  name=23.124.167.115.b.barracudacentral.org type=A: Host not found, try
  again

  Jun  2 10:04:33 mx1 postfix/smtpd[89019]: warning:
  17.204.24.8.b.barracudacentral.org: RBL lookup error: Host or domain
  name not found. Name service error for
  name=17.204.24.8.b.barracudacentral.org type=A: Host not found, try
  again

  Jun  2 10:04:37 mx1 postfix/postscreen[55753]: warning: dnsblog reply
  timeout 10s for b.barracudacentral.org

These lines are interspersed among others that indicate more normal
activity with b.barracudacentral.org, e.g.:

  Jun  2 10:04:10 mx1 postfix/dnsblog[55985]: addr 199.30.50.35 listed by 
domain b.barracudacentral.org as 127.0.0.2
  Jun  2 10:04:47 mx1 postfix/dnsblog[66369]: addr 157.56.112.23 listed by 
domain b.barracudacentral.org as 127.0.0.2

I know this is not an issue with Postfix (which dutifully reports the
TRY_AGAIN it receives from the system library), but I wonder if anyone
else is seeing this from barracuda?  Based on a week's worth of logs, I
do not see even a single instance of this problem with any other RBL
(and we query several).

I've separately engaged our DNS admins in case they could offer some
insight, but it would be interesting to learn if others are experiencing
the same issue /only/ with barracuda.



Re: AOL declines mails with 421dnsnr on one of our nodes

2012-06-02 Thread Christian Parpart
On Sat, Jun 2, 2012 at 5:24 PM, Wietse Venema wie...@porcupine.org wrote:

 Christian Parpart:
  But the outgoing IP is set up with DNS properly, however.

 You have told everything but the IP address, so how can we help?


46.231.176.107

sorry, I thought that weren't really required :-)
So long,
Christian.


Re: mynetworks support for ipv6 link local (fe80) hosts

2012-06-02 Thread Viktor Dukhovni
On Sat, Jun 02, 2012 at 12:31:10PM -0400, Derek Atkins wrote:

 And I'm pretty sure that this is the patch (to postfix!) that fixed the
 problem for me.  Once I upgraded from 2.7.7 to 2.9.2 not only did my
 configuration suddenly start working, but lo and behold the log messages
 changed, too!

You're right. From the Postfix HISTORY file:

20101108

Workaround: strip off IPv6 datalink suffix from peer address 
to avoid problems with strict address checking code. Files:
smtpd/smtpd_peer.c, qmqpd/qmqpd_peer.c.

This change appeared in Postfix 2.8-20101126, thus official releases
starting with 2.8.0 partly support link-local IPv6 addresses.

-- 
Viktor.


Re: [OT] frequent TRY_AGAINs and 10s timeouts, but *only* with b.barracudacentral.org

2012-06-02 Thread njo...@vbhcs.org


Sahil Tandon sahil+post...@tandon.net wrote:

I am seeing hundreds (on higher volume days, over a thousand) of lines
like:

 Jun  2 10:04:30 mx1 postfix/dnsblog[58868]: warning: dnsblog_query:
 lookup error for DNS query 23.124.167.115.b.barracudacentral.org: Host
 or domain name not found. Name service error for
 name=23.124.167.115.b.barracudacentral.org type=A: Host not found, try
 again


Yes, a few to dozens on my fairly low volume servers for the last couple weeks. 
 Only barracuda, never any of the other popular lists.  So far I just ignore it.



--
Noel Jones
Sent from my mobile.  Sorry.


Re: [OT] frequent TRY_AGAINs and 10s timeouts, but *only* with b.barracudacentral.org

2012-06-02 Thread Ned Slider

On 02/06/12 17:44, Sahil Tandon wrote:

I am seeing hundreds (on higher volume days, over a thousand) of lines
like:

  Jun  2 10:04:30 mx1 postfix/dnsblog[58868]: warning: dnsblog_query:
  lookup error for DNS query 23.124.167.115.b.barracudacentral.org: Host
  or domain name not found. Name service error for
  name=23.124.167.115.b.barracudacentral.org type=A: Host not found, try
  again

  Jun  2 10:04:33 mx1 postfix/smtpd[89019]: warning:
  17.204.24.8.b.barracudacentral.org: RBL lookup error: Host or domain
  name not found. Name service error for
  name=17.204.24.8.b.barracudacentral.org type=A: Host not found, try
  again

  Jun  2 10:04:37 mx1 postfix/postscreen[55753]: warning: dnsblog reply
  timeout 10s for b.barracudacentral.org

These lines are interspersed among others that indicate more normal
activity with b.barracudacentral.org, e.g.:

  Jun  2 10:04:10 mx1 postfix/dnsblog[55985]: addr 199.30.50.35 listed by 
domain b.barracudacentral.org as 127.0.0.2
  Jun  2 10:04:47 mx1 postfix/dnsblog[66369]: addr 157.56.112.23 listed by 
domain b.barracudacentral.org as 127.0.0.2

I know this is not an issue with Postfix (which dutifully reports the
TRY_AGAIN it receives from the system library), but I wonder if anyone
else is seeing this from barracuda?  Based on a week's worth of logs, I
do not see even a single instance of this problem with any other RBL
(and we query several).

I've separately engaged our DNS admins in case they could offer some
insight, but it would be interesting to learn if others are experiencing
the same issue /only/ with barracuda.



I see similar in my bind logs on a server running SpamAssassin. The 
barracuda RBL is queried by default in SpamAssassin so I suspect the 
volume of queries they receive is pretty high. I assume it's a load 
issue at their end.


I've been seeing such entries in my logs for months but it does seen to 
have got worse since around April of this year.


I see similar log entries for sa-accredit.habeas.com which is also 
queried by SpamAssassin.


Those are the only two that stand out in my logs from the multitude of 
RBLs queried.






software for sending large files?

2012-06-02 Thread Miles Fidelman

Hi Folks,

I figure someone here might know

There are a whole bunch of services for emailing large files - mainly 
by allowing one to upload the file, then sending an email to one's 
intended recipient that contains a download link (e.g., filemail.com).  
I also know of at least one list manager (sympa) that will do this for 
large file attachments (they call it urlizing the file).  For that 
matter, tweet-a-file does the same thing for twitter.


But... for the life of me, I can't seem to find a server-side program 
that I can run to do this on our system.  The basic use case:


- tweak our postfix configuration so that instead of rejecting large 
file attachments, it pipes them to a script that:

-- stores the file
-- generates a unique URL that points to the file
-- generates a password that goes with the URL
-- email the URL and password to the original recipient

I know that I've seen scripts like this in the past, but I've been 
drawing a blank in trying to track one down today.


Thanks for any pointers.

Miles Fidelman

--
In theory, there is no difference between theory and practice.
In practice, there is.    Yogi Berra




Re: software for sending large files?

2012-06-02 Thread Benny Pedersen

Den 2012-06-03 01:15, Miles Fidelman skrev:

I figure someone here might know


[snip]

bittorrent, with webseeds and or dht only option, then torrent can be 
sent over email, and recipient fetch the file from the sender via 
torrent protocol


unlimit size :=)





Re: [OT] frequent TRY_AGAINs and 10s timeouts, but *only* with b.barracudacentral.org

2012-06-02 Thread Stan Hoeppner
On 6/2/2012 11:44 AM, Sahil Tandon wrote:

  Jun  2 10:04:30 mx1 postfix/dnsblog[58868]: warning: dnsblog_query:
  lookup error for DNS query 23.124.167.115.b.barracudacentral.org: Host
  or domain name not found. Name service error for
  name=23.124.167.115.b.barracudacentral.org type=A: Host not found, try
  again

 I know this is not an issue with Postfix (which dutifully reports the
 TRY_AGAIN it receives from the system library), but I wonder if anyone
 else is seeing this from barracuda?

~$ grep b.barracudacentral.org /var/log/mail.warn

May 30 01:35:14 greer postfix/smtpd[343]: warning:
62.214.85.209.b.barracudacentral.org: RBL lookup error: Host or domain
name not found. Name service error for
name=62.214.85.209.b.barracudacentral.org type=A: Host not found, try again

May 31 08:05:14 greer postfix/smtpd[30807]: warning:
45.162.165.188.b.barracudacentral.org: RBL lookup error: Host or domain
name not found. Name service error for
name=45.162.165.188.b.barracudacentral.org type=A: Host not found, try again

May 31 12:32:49 greer postfix/smtpd[26129]: warning:
107.3.19.23.b.barracudacentral.org: RBL lookup error: Host or domain
name not found. Name service error for
name=107.3.19.23.b.barracudacentral.org type=A: Host not found, try again

May 31 14:04:48 greer postfix/smtpd[3633]: warning:
54.11.138.188.b.barracudacentral.org: RBL lookup error: Host or domain
name not found. Name service error for
name=54.11.138.188.b.barracudacentral.org type=A: Host not found, try again

This seems to be par for the course with BRBL.  I first configured it
when it was all a buzz some years ago, and every query resulted in these
errors, so I ditched it.  I enabled it again some year(s) later, and for
the most part queries are answered.  My MX runs only 500-1000 connects
per day, and a few failures a day isn't a show stopper.  It still stops
a decent amount of spam.

I'd guess they have some sort of (perennial) load balancing issues with
their servers, or simply need to add more (geographically dispersed)
servers.

The problem isn't on your end Sahil.

-- 
Stan


Re: AOL declines mails with 421dnsnr on one of our nodes

2012-06-02 Thread Stan Hoeppner
On 6/2/2012 12:21 PM, Christian Parpart wrote:

 46.231.176.107

~$ host 46.231.176.107
107.176.231.46.in-addr.arpa domain name pointer cesar1.dawanda.com.

~$ host cesar1.dawanda.com
cesar1.dawanda.com has address 46.231.176.107

Looks good querying from my local resolver in net 65.40.0.0/15.

-- 
Stan


Re: software for sending large files? - solution found

2012-06-02 Thread Miles Fidelman

Benny Pedersen wrote:

Den 2012-06-03 01:15, Miles Fidelman skrev:

I figure someone here might know


[snip]

bittorrent, with webseeds and or dht only option, then torrent can be 
sent over email, and recipient fetch the file from the sender via 
torrent protocol

unlimit size :=)

for anyone who might be interested... with a LOT of googling, I found this:

http://fex.rus.uni-stuttgart.de/
- GPL'd source version: http://fex.rus.uni-stuttgart.de/
- Debian Package: http://packages.debian.org/sid/fex
- hosted version: http://fex.rus.uni-stuttgart.de/fup




--
In theory, there is no difference between theory and practice.
In practice, there is.    Yogi Berra




Re: software for sending large files? - solution found

2012-06-02 Thread Yashodhan Barve
On 12-06-02 8:39 PM, Miles Fidelman wrote:
 Benny Pedersen wrote:
 Den 2012-06-03 01:15, Miles Fidelman skrev:
 I figure someone here might know

 [snip]

 bittorrent, with webseeds and or dht only option, then torrent can be
 sent over email, and recipient fetch the file from the sender via
 torrent protocol
 unlimit size :=)
 for anyone who might be interested... with a LOT of googling, I found this:
 
 http://fex.rus.uni-stuttgart.de/
 - GPL'd source version: http://fex.rus.uni-stuttgart.de/
 - Debian Package: http://packages.debian.org/sid/fex
 - hosted version: http://fex.rus.uni-stuttgart.de/fup
 
 
 
 
Take a look at http://zend.to/

regards
yashodhan



postfix/virtual can't deliver to virtual mailbox

2012-06-02 Thread Alvin Wong
Hi,

I am running postfix 2.6.6 on CentOS 6.2.
I set up postfix to use virtual mailbox referring to this
(http://www.postfix.org/VIRTUAL_README.html#virtual_mailbox)

When the server starts, it can't deliver mail to virtual mailbox
(mails are stuck in the queue).
I see this in the maillog:

~~
Jun  2 20:35:43 localhost postfix/virtual[2122]: fatal: open lock file
pid/unix.virtual: cannot open file: Permission denied
Jun  2 20:35:44 localhost postfix/master[1784]: warning: process
/usr/libexec/postfix/virtual pid 2122 exit status 1
Jun  2 20:35:44 localhost postfix/master[1784]: warning:
/usr/libexec/postfix/virtual: bad command startup -- throttling
~~

However, when I execute `postfix stop; postfix start` in shell,
postfix starts delivering mail to virtual mailbox and the message
didn't appear again.
But then when the machine is restarted (both warm reboot and cold
reboot), the problem appears again. The only fix I know is to execute
`postfix stop; postfix start` manually.

The file: `/var/spool/postfix/pid/unix.virtual` is owned by root and
has permission 0600 (rw for root only). It was set with `postfix
set-permissions`.

This is quite strange because when the server boots and start postfix
automatically, it is supposed to do the same as `postfix start`.
Anyone have any idea?

Thanks,
Alvin Wong