Major Bug!!
Dear Wietse, There is a bug in Postfix that should looked at immediately. FRom http://groups.google.com/group/alt.comp.mail.postfix/browse_thread/thread/fa83dc31cec1194e# In case you think I am being pompous, I am not. Found the problem, a filter was set to 120.0.0.1 instead of 127.0.0.1 . I thought it was fixed. Even after 'fixing' this problem, postfix still insisted the filter was at 120.0.0.1 . All right I do not mind the smtp_fallback_relay , but this indicates a bug somewhere in postfix. Even if told to change directions, it was still looking for the wrong server? I tried both 2.7.0 and 2.8 experimental! The debugging sectin help and stil we have a back up of e-mail. PLEASE fix! -- Member - Liberal International This is doc...@nl2k.ab.ca Ici doc...@nl2k.ab.ca God, Queen and country! Never Satan President Republic! Beware AntiChrist rising! http://twitter.com/rootnl2k http://www.facebook.com/dyadallee UK Time for a Common Sense change vote Liberal Democrat / Alliance
Re: Major Bug!!
On 4/21/2010 1:20 PM, The Doctor wrote: Dear Wietse, There is a bug in Postfix that should looked at immediately. FRom http://groups.google.com/group/alt.comp.mail.postfix/browse_thread/thread/fa83dc31cec1194e# In case you think I am being pompous, I am not. Found the problem, a filter was set to 120.0.0.1 instead of 127.0.0.1 . I thought it was fixed. Even after 'fixing' this problem, postfix still insisted the filter was at 120.0.0.1 . All right I do not mind the smtp_fallback_relay , but this indicates a bug somewhere in postfix. Even if told to change directions, it was still looking for the wrong server? I tried both 2.7.0 and 2.8 experimental! The debugging sectin help and stil we have a back up of e-mail. PLEASE fix! Have you by chance looked at: man postsuper and reference the -r parameter? -Matt
Re: Major Bug!!
On Wed, Apr 21, 2010 at 11:20:11AM -0600, The Doctor wrote: Dear Wietse, There is a bug in Postfix that should looked at immediately. Dear Doctor, if you don't want to be rediculed and summarily dismissed, ask humbly for clarification of how things are expected to work and whether what you are experiencing is expected behaviour before making wild accusations and implying that someone owes you immediate support for free software. http://groups.google.com/group/alt.comp.mail.postfix/browse_thread/thread/fa83dc31cec1194e# In case you think I am being pompous, I am not. I am afraid only others can refute this claim, you are not in a position to do so. Found the problem, a filter was set to 120.0.0.1 instead of 127.0.0.1 . I thought it was fixed. The content filter of already accepted messages is a queue-file property. As documented, files already in the queue need to be reprocesed with new filter settings: http://www.postfix.org/FILTER_README.html#advanced_turnoff In your case to correct rather than disable the filter, but the idea is the same. All right I do not mind the smtp_fallback_relay , but this indicates a bug somewhere in postfix. Even if told to change directions, it was still looking for the wrong server? I tried both 2.7.0 and 2.8 experimental! The debugging sectin help and stil we have a back up of e-mail. PLEASE fix! This is the last time you get any help with that tone. Future violations will lead to the termination of your list subscription. -- Viktor. P.S. Morgan Stanley is looking for a New York City based, Senior Unix system/email administrator to architect and sustain our perimeter email environment. If you are interested, please drop me a note.
Re: Major Bug!!
The Doctor: Found the problem, a filter was set to 120.0.0.1 instead of 127.0.0.1 . I thought it was fixed. Even after 'fixing' this problem, postfix still insisted the filter was at 120.0.0.1 . See the postsuper -r option: http://www.postfix.org/postsuper.1.html This is also referenced from: http://www.postfix.org/FILTER_README.html#advanced_turnoff Which describes what to do when you change your mind about the current content_filter setting. Wietse
